os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add the Errata notice processing procedures for 4.11.

Browse source
This commit is contained in:
Ken Smith 2005-03-06 10:46:47 +00:00
parent 48eb2ae5ce
commit 4642722186
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=24003
2 changed files with 59 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

3
en/releases/4.11R/Makefile
View file

@ -1,4 +1,4 @@
# $FreeBSD: www/en/releases/4.11R/Makefile,v 1.2 2005/01/25 17:01:06 hrs Exp $
# $FreeBSD: www/en/releases/4.11R/Makefile,v 1.3 2005/01/25 17:07:51 hrs Exp $
.if exists(../Makefile.conf)
.include "../Makefile.conf"
@ -13,6 +13,7 @@ DOCS+= installation.sgml
DOCS+= relnotes.sgml
DOCS+= schedule.sgml
DOCS+= todo.sgml
DOCS+= errata_policy.sgml
DATA= docbook.css
DATA+= errata.html

57
en/releases/4.11R/errata_policy.sgml Normal file
View file

@ -0,0 +1,57 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY email 'freebsd-qa'>
<!ENTITY date "$FreeBSD$">
<!ENTITY local.rel "4.11">
<!ENTITY local.rel.tag "4_11">
<!ENTITY title "FreeBSD &local.rel; Errata Processing Policy">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<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>
&footer;
</body>
</html>