BSD 4_4 release

[unix-history] / usr / src / share / doc / papers / relengr / 0.t

diff --git a/usr/src/share/doc/papers/relengr/0.t b/usr/src/share/doc/papers/relengr/0.t
index 7feb878..7fb3290 100644 (file)
--- a/usr/src/share/doc/papers/relengr/0.t
+++ b/usr/src/share/doc/papers/relengr/0.t
@@ -1,5 +1,40 @@
-.\"    @(#)0.t 1.1     (Copyright 1989 M. K. McKusick) 89/02/18
+.\" Copyright (c) 1989 The Regents of the University of California.
+.\" All rights reserved.
+.\"
+.\" Redistribution and use in source and binary forms, with or without
+.\" modification, are permitted provided that the following conditions
+.\" are met:
+.\" 1. Redistributions of source code must retain the above copyright
+.\"    notice, this list of conditions and the following disclaimer.
+.\" 2. Redistributions in binary form must reproduce the above copyright
+.\"    notice, this list of conditions and the following disclaimer in the
+.\"    documentation and/or other materials provided with the distribution.
+.\" 3. All advertising materials mentioning features or use of this software
+.\"    must display the following acknowledgement:
+.\"    This product includes software developed by the University of
+.\"    California, Berkeley and its contributors.
+.\" 4. Neither the name of the University nor the names of its contributors
+.\"    may be used to endorse or promote products derived from this software
+.\"    without specific prior written permission.
+.\"
+.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
+.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
+.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
+.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
+.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
+.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
+.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
+.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
+.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
+.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
+.\" SUCH DAMAGE.
+.\"
+.\"    @(#)0.t 5.1 (Berkeley) 4/17/91
+.\"

 .rm CM
 .rm CM

+.nr PO 1.25i
+.ds CH "
+.ds CF "%

 .nr Fn 0 1
 .ds b3 4.3\s-1BSD\s+1
 .de KI
 .nr Fn 0 1
 .ds b3 4.3\s-1BSD\s+1
 .de KI


@@ -9,7 +44,7 @@
 Figure \\n(Fn - \\$1.
 ..
 .de SM
 Figure \\n(Fn - \\$1.
 ..
 .de SM

-\\s-1\\$1\\s+1
+\\s-1\\$1\\s+1\\$2

 ..
 .de NM
 \&\fI\\$1\fP\\$2
 ..
 .de NM
 \&\fI\\$1\fP\\$2


@@ -21,11 +56,13 @@ Figure \\n(Fn - \\$1.
 \&\fB\\$1\fP\\$2
 ..
 .TL
 \&\fB\\$1\fP\\$2
 ..
 .TL

-The Release Engineering of 4.3BSD
+The Release Engineering of 4.3\s-1BSD\s0

 .AU
 Marshall Kirk McKusick
 .AU
 Michael J. Karels
 .AU
 Marshall Kirk McKusick
 .AU
 Michael J. Karels

+.AU
+Keith Bostic

 .AI
 Computer Systems Research Group
 Computer Science Division
 .AI
 Computer Systems Research Group
 Computer Science Division


@@ -33,15 +70,22 @@ Department of Electrical Engineering and Computer Science
 University of California, Berkeley
 Berkeley, California  94720
 .AB
 University of California, Berkeley
 Berkeley, California  94720
 .AB

-This paper gives a brief overview of the release engineering
-techniques used during the release of the 4.3BSD UNIX\(dg
+This paper describes an approach used by a small group of people
+to develop and integrate a large software system.
+It details the development and release engineering strategy
+used during the preparation of the \*(b3 version of the UNIX\(dg

 .FS
 \(dgUNIX is a registered trademark of AT&T in the US and other countries.
 .FE
 operating system.
 .FS
 \(dgUNIX is a registered trademark of AT&T in the US and other countries.
 .FE
 operating system.

-It describes the approach that a small group of people can
-use to develop and integrate a large software system.
-It then describes the three step methodology used to
-engineer a clean, correct, and coherent release.
+Each release cycle is divided into an initial development phase
+followed by a release engineering phase.
+The release engineering of the distribution is done in three steps.
+The first step has an informal control policy for tracking modifications;
+it results in an alpha distribution.
+The second step has more rigid change mechanisms in place;
+it results in a beta release.
+During the final step changes are tracked very closely;
+the result is the final distribution.

 .AE
 .LP
 .AE
 .LP