From 6c2a9efa62fec09320d3ed0a6e9647f2a5468eba Mon Sep 17 00:00:00 2001 From: Scott Long Date: Tue, 24 May 2005 03:29:38 +0000 Subject: [PATCH] Add the errata policy document for 5.4 (copied from 5.3). --- en/releases/5.4R/Makefile | 4 +-- en/releases/5.4R/errata_policy.sgml | 54 +++++++++++++++++++++++++++++ 2 files changed, 56 insertions(+), 2 deletions(-) create mode 100644 en/releases/5.4R/errata_policy.sgml diff --git a/en/releases/5.4R/Makefile b/en/releases/5.4R/Makefile index e546f1e924..6b5151244e 100644 --- a/en/releases/5.4R/Makefile +++ b/en/releases/5.4R/Makefile @@ -1,4 +1,4 @@ -# $FreeBSD: www/en/releases/5.4R/Makefile,v 1.4 2005/05/09 16:47:59 hrs Exp $ +# $FreeBSD: www/en/releases/5.4R/Makefile,v 1.5 2005/05/09 20:48:20 murray Exp $ .if exists(../Makefile.conf) .include "../Makefile.conf" @@ -7,7 +7,7 @@ .include "../Makefile.inc" .endif -DOCS= todo.sgml schedule.sgml +DOCS= todo.sgml schedule.sgml errata_policy.sgml DOCS+= announce.sgml DOCS+= hardware.sgml DOCS+= installation.sgml diff --git a/en/releases/5.4R/errata_policy.sgml b/en/releases/5.4R/errata_policy.sgml new file mode 100644 index 0000000000..7c34520e11 --- /dev/null +++ b/en/releases/5.4R/errata_policy.sgml @@ -0,0 +1,54 @@ + + + + + + + %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 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; + + +