From 46427221867603409d991dd963d45fdfdaf61aeb Mon Sep 17 00:00:00 2001 From: Ken Smith Date: Sun, 6 Mar 2005 10:46:47 +0000 Subject: [PATCH] Add the Errata notice processing procedures for 4.11. --- en/releases/4.11R/Makefile | 3 +- en/releases/4.11R/errata_policy.sgml | 57 ++++++++++++++++++++++++++++ 2 files changed, 59 insertions(+), 1 deletion(-) create mode 100644 en/releases/4.11R/errata_policy.sgml diff --git a/en/releases/4.11R/Makefile b/en/releases/4.11R/Makefile index 21d79e55b4..9de33caf72 100644 --- a/en/releases/4.11R/Makefile +++ b/en/releases/4.11R/Makefile @@ -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 diff --git a/en/releases/4.11R/errata_policy.sgml b/en/releases/4.11R/errata_policy.sgml new file mode 100644 index 0000000000..3cf92588de --- /dev/null +++ b/en/releases/4.11R/errata_policy.sgml @@ -0,0 +1,57 @@ + + + + + + + %includes; +]> + + +&header; + +

Introduction

+

The following is the general policy for submitting requests to have + Errata Fixes applied to FreeBSD &local.rel;.

+ +

Procedures

+

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.

+ +

Policy

+

Errata Candidates

+

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.

+ +

Initial Patch

+

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.

+ +

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 + re@FreeBSD.org. Please include + the patch that will need to be applied to &local.rel; and who has + reviewed the fix.

+ +&footer; + + +