The following is the general policy for submitting requests to have + Errata Fixes applied to FreeBSD &local.rel;.
+ +The Errata fixes will be applied by a member of the Release Engineering + Team, coordinating the fix with the Security Officer who owns the branch. + An Errata Notice will also be issued. The Release Engineering Team may + choose to handle several Errata with one Errata Notice if several are + being processed at roughly the same time.
+ +The classification of things that are Errata candidates are things + that are severe service-disrupting bugs for which there is no known + work-around. Things like bugs in device drivers that impair their + expected functionality, things that can cause kernel panics, etc.
+ +During the initial phases the fix for Errata should be handled + exactly like any other fix. It should initially be committed to + HEAD and go through the normal testing period there. The fix should + then be MFCed as usual. At this point if you feel a fix is an Errata + Notice candidate please contact the Release Engineering Team to make + them aware of it.
+ +The fix should then sit in RELENG_5 for one to two weeks. During + this period please try to have the fix reviewed by another senior + Developer familiar with the section of the code you are working with. + You should also get confirmation that the fix solves the problem from + someone who had reported the problem. Assuming no problems come up + during this testing period then send in the formal request to + re@FreeBSD.org. Please include + the patch that will need to be applied to &local.rel; and who has + reviewed the fix.
+ +&footer; + + +