diff options
Diffstat (limited to 'en_US.ISO8859-1/htdocs/releases/4.11R/errata_policy.xml')
| -rw-r--r-- | en_US.ISO8859-1/htdocs/releases/4.11R/errata_policy.xml | 61 |
1 files changed, 0 insertions, 61 deletions
diff --git a/en_US.ISO8859-1/htdocs/releases/4.11R/errata_policy.xml b/en_US.ISO8859-1/htdocs/releases/4.11R/errata_policy.xml deleted file mode 100644 index 5b9b7ed551..0000000000 --- a/en_US.ISO8859-1/htdocs/releases/4.11R/errata_policy.xml +++ /dev/null @@ -1,61 +0,0 @@ -<?xml version="1.0" encoding="iso-8859-1"?> -<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN" -"http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [ -<!ENTITY email 'freebsd-qa'> -<!ENTITY local.rel "4.11"> -<!ENTITY local.rel.tag "4_11"> -<!ENTITY title "FreeBSD &local.rel; Errata Processing Policy"> -]> - -<html xmlns="http://www.w3.org/1999/xhtml"> -<head> - <title>&title;</title> - - <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword> - </head> - - <body class="navinclude.download"> - - <h1>Introduction</h1> - <p>The following is the general policy for submitting requests to have - Errata Fixes applied to FreeBSD &local.rel;.</p> - - <h1>Procedures</h1> - <p>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.</p> - - <h1>Policy</h1> - <h2>Errata Candidates</h2> - <p>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.</p> - - <h2>Initial Patch</h2> - <p>During the initial phases the fix for Errata should be - handled exactly like any other fix. It should initially - be committed to HEAD if possible and go through the normal - testing period there. The fix should then be MFCed as usual. - Since HEAD and RELENG_5 have become dramatically different - from RELENG_4 in many areas this may not be possible, and - the initial commit may need to be applied straight to - RELENG_4. 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.</p> - - <p>The fix should then sit in RELENG_4 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 - <a href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>. Please include - the patch that will need to be applied to &local.rel; and who has - reviewed the fix.</p> - - -</body> -</html> |