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

Initial pass at setting up the 4.11 release docs. Schedule might need

Browse source 
a 'reality check' from Scott.  Not hooking it up to the build yet.
This commit is contained in:
Ken Smith 2004-11-30 05:12:40 +00:00
parent a0ac91ca9b
commit a10be0b91d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=23072
4 changed files with 547 additions and 0 deletions

15
en/releases/4.11R/Makefile Normal file
View file

@ -0,0 +1,15 @@
# $FreeBSD$
.if exists(../Makefile.conf)
.include "../Makefile.conf"
.endif
.if exists(../Makefile.inc)
.include "../Makefile.inc"
.endif
DOCS= schedule.sgml
DOCS+= todo.sgml
DATA= docbook.css
.include "${WEB_PREFIX}/share/mk/web.site.mk"

165
en/releases/4.11R/docbook.css Normal file
View file

@ -0,0 +1,165 @@
/*
* Copyright (c) 2001, 2003 The FreeBSD Documentation Project
* 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.
*
* THIS SOFTWARE IS PROVIDED BY THE AUTHOR 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 AUTHOR 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.
*
* $FreeBSD$
*/
BODY ADDRESS {
line-height: 1.3;
margin: .6em 0;
}
BODY BLOCKQUOTE {
margin-top: .75em;
line-height: 1.5;
margin-bottom: .75em;
}
HTML BODY {
margin: 1em 8% 1em 10%;
line-height: 1.2;
}
.LEGALNOTICE {
font-size: small;
font-variant: small-caps;
}
BODY DIV {
margin: 0;
}
DL {
margin: .8em 0;
line-height: 1.2;
}
BODY FORM {
margin: .6em 0;
}
H1, H2, H3, H4, H5, H6,
DIV.EXAMPLE P B,
.QUESTION,
DIV.TABLE P B,
DIV.PROCEDURE P B {
color: #990000;
}
BODY H1 {
margin: .8em 0 0 -4%;
line-height: 1.3;
}
BODY H2 {
margin: .8em 0 0 -4%;
line-height: 1.3;
}
BODY H3 {
margin: .8em 0 0 -3%;
line-height: 1.3;
}
BODY H4 {
margin: .8em 0 0 -3%;
line-height: 1.3;
}
BODY H5 {
margin: .8em 0 0 -2%;
line-height: 1.3;
}
BODY H6 {
margin: .8em 0 0 -1%;
line-height: 1.3;
}
BODY HR {
margin: .6em
}
BODY IMG.NAVHEADER {
margin: 0 0 0 -4%;
}
OL {
margin: 0 0 0 5%;
line-height: 1.2;
}
BODY P {
margin: .6em 0;
line-height: 1.2;
}
BODY PRE {
margin: .75em 0;
line-height: 1.0;
color: #461b7e;
}
BODY TD {
line-height: 1.2
}
BODY TH {
line-height: 1.2;
}
UL, BODY DIR, BODY MENU {
margin: 0 0 0 5%;
line-height: 1.2;
}
HTML {
margin: 0;
padding: 0;
}
.FILENAME {
color: #007a00;
}
BODY H1, BODY H2, BODY H3, BODY H4, BODY H5, BODY H6 {
margin-left: 0
}
.GUIMENU, .GUIMENUITEM, .GUISUBMENU,
.GUILABEL, .INTERFACE, .GUIBUTTON,
.SHORTCUT, .SHORTCUT .KEYCAP {
background-color: #F0F0F0;
}
.ACCEL {
background-color: #F0F0F0;
text-decoration: underline;
}
.PROGRAMLISTING, .SCREEN {
margin-left: 3ex;
}

304
en/releases/4.11R/schedule.sgml Normal file
View file

@ -0,0 +1,304 @@
<!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; Release Process">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
]>
<html>
&header;
<h1>Introduction</h1>
<p>This is a specific schedule for the release of FreeBSD &local.rel;. For
more general information about the release engineering process,
please see the <a href="&base;/releng/index.html">Release
Engineering</a> section of the web site.</p>
<p>General discussions about the release engineering process or
quality assurance issues should be sent to the public <a
href="mailto:FreeBSD-qa@FreeBSD.org">freebsd-qa</a> mailing list.
<a
href="&base;/doc/en_US.ISO8859-1/books/faq/misc.html#DEFINE-MFC">MFC</a>
requests should be sent to <a
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>.</p>
<h1>Schedule</h1>
<table border=1>
<tr><td>Action</td><td>Expected</td><td>Actual</td><td>Description</td>
</tr>
<tr>
<td>Reminder announcement</td>
<td>30&nbsp;Nov&nbsp;2004</td>
<td>--</td>
<td>Release Engineers send announcement email to
<tt>developers@FreeBSD.org</tt> with a rough schedule for the FreeBSD
&local.rel; release.</td>
</tr>
<tr>
<td>&local.rel;-BETA Testing Guide published</td>
<td>--</td>
<td>--</td>
<td>A <a href="&base;/releases/&local.rel;R/qa.html">testing guide</a>
should be published with information about recent changes and
areas of the system that should be thoroughly tested during the
pre-release/RC period.</td>
</tr>
<tr>
<td>Announce the Ports Freeze</td>
<td>--</td>
<td>--</td>
<td>Someone from <tt>portmgr@</tt> should email
<tt>freebsd-ports@</tt> and BCC: <tt>developers@</tt> to set a date
for the week long ports freeze and tagging of the ports tree.</td>
</tr>
<tr>
<td><tt>&local.rel;-PRERELEASE</tt></td>
<td>6&nbsp;Dec&nbsp;2004</td>
<td>--</td>
<td><tt>newvers.sh</tt>, and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>Code freeze begins</td>
<td>13&nbsp;Dec&nbsp;2004</td>
<td>--</td>
<td>After this date, all commits to the <tt>RELENG_4</tt> branch
must be approved by <a
href="mailto:re@FreeBSD.org">re@FreeBSD.org</a>. Certain highly
active documentation committers are exempt from this rule for
routine man page / release note updates. Heads-up emails
should be sent to the <tt>developers@</tt>, <tt>stable@</tt>
and <tt>qa@</tt> lists.</td>
</tr>
<tr>
<td><tt>RELENG_&local.rel.tag;</tt> branch</td>
<td>27&nbsp;Dec&nbsp;2004</td>
<td>--</td>
<td>The release branch is created.</td>
</tr>
<tr>
<td>Unfreeze the tree</td>
<td>27&nbsp;Dec&nbsp;2004</td>
<td>--</td>
<td>Announcement to <tt>developers@</tt> explaining that
commits to <tt>RELENG_4</tt> no longer require approval. Also
note the policy for commits to the <tt>RELENG_&local.rel.tag;</tt>
branch.</td>
</tr>
<tr>
<td><tt>&local.rel;-RC</tt></td>
<td>27&nbsp;Dec&nbsp;2004</td>
<td>--</td>
<td><tt>newvers.sh</tt> and <tt>release.ent</tt> updated.</td>
</tr>
<tr>
<td>First release candidate</td>
<td>3&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>The first release candidate for the x86 and Alpha architecture is
released. ISO images should be uploaded to
<tt>ftp-master.FreeBSD.org</tt>. A network install directory should
be uploaded to <tt>ftp-master.FreeBSD.org</tt>. The
<tt>packages/</tt> directory should be a <em>relative</em> symlink,
as described in the releng article. When the builds begin send a note to
<a href="mailto:mirror-announce@FreeBSD.org">mirror-announce@FreeBSD.org</a>
saying a "Normal Release Cycle" is beginning, RC ISOs and install
directories will be coming through the next few weeks.</td>
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>3&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the first snapshot is uploaded.</td>
</tr>
<tr>
<td>Second release candidate</td>
<td>10&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>Note: the release date of this candidate depends on the user
experience with RC1.</td>
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>10&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the second snapshot is uploaded.</td>
</tr>
<tr>
<td>Third release candidate</td>
<td>17&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>Note: the release date of this candidate depends on the user
experience with RC2.</td>
</tr>
<tr>
<td>Heads up to <tt>-stable</tt></td>
<td>17&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
<tt>stable@FreeBSD.org</tt> after the third snapshot is uploaded.</td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<tr>
<td>Ports tree frozen</td>
<td>--</td>
<td>--</td>
<td>Only approved commits will be permitted to the <tt>ports/</tt>
tree during the freeze.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td>Announce <tt>doc/</tt> tree slush</td>
<td>--</td>
<td>--</td>
<td>Notification of the impending <tt>doc/</tt> tree slush should
be sent to <tt>doc@</tt>.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree slush</td>
<td>--</td>
<td>--</td>
<td>Non-essential commits to the <tt>en_US.ISO8859-1/</tt> subtree
should be delayed from this point until after the <tt>doc/</tt>
tree tagging, to give translation teams time to synchronize
their work.</td>
</tr>
<!-- portmgr should tweak these values after we commit it to CVS -->
<!-- packages should be loaded on ftp-master at least two days before -->
<!-- release bits get loaded to avoid network congestion problems -->
<tr>
<td>Ports tree tagged</td>
<td>--</td>
<td>--</td>
<td><tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>ports/</tt>.</td>
</tr>
<tr>
<td>Ports tree unfrozen</td>
<td>--</td>
<td>--</td>
<td>After the <tt>ports/</tt> tree is tagged,
the <tt>ports/</tt> tree will be re-opened for commits, but
commits made after tagging will not go in &local.rel;-RELEASE.</td>
</tr>
<tr>
<td>Final package build starts</td>
<td>--</td>
<td>--</td>
<td>The ports cluster and <a href="http://bento.FreeBSD.org">bento</a>
build final packages.</td>
</tr>
<!-- doceng should tweak these values after we commit it to CVS -->
<tr>
<td><tt>doc/</tt> tree tagged.</td>
<td>--</td>
<td>--</td>
<td>Version number bumps for <tt>doc/</tt> subtree.
<tt>RELEASE_&local.rel.tag;_0</tt> tag for <tt>doc/</tt>. <tt>doc/</tt>
slush ends at this time.</td>
</tr>
<tr>
<td>Version numbers bumped.</td>
<td>20&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>The files listed <a
href="&base;/doc/en_US.ISO8859-1/articles/releng/article.html#VERSIONBUMP">here</a>
are updated to reflect the fact that this is FreeBSD &local.rel;.</td>
</tr>
<tr>
<td>src tree tagged.</td>
<td>20&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td><tt>RELENG_&local.rel.tag;_0_RELEASE</tt> tag for <tt>src/</tt>.</td>
</tr>
<tr>
<td>Final builds.</td>
<td>20&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>Final builds for x86 and Alpha in a pristine environment.</td>
</tr>
<tr>
<td>Warn <tt>mirror-announce@FreeBSD.org</tt></td>
<td>21&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>Heads up email to <a
href="mailto:mirror-announce@FreeBSD.org">mirror-announce@FreeBSD.org</a>
to give admins time to prepare for the load spike to come. The
site administrators have frequently requested advance notice for
new ISOs.</td>
</tr>
<tr>
<td>Upload to <tt>ftp-master</tt>.</td>
<td>22&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>Release uploaded to <tt>ftp-master.FreeBSD.org</tt> (packages
should have been done before now, otherwise it chokes the mirror
sites and propagation of the release bits takes too long)</td>
</tr>
<tr>
<td>Update man.cgi on the website.</td>
<td>24&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>Make sure the &local.rel; manual pages are being displayed by default
for the man->web gateway. Also make sure these man pages are
pointed to by docs.sgml.</td>
</tr>
<tr>
<td>Announcement</td>
<td>24&nbsp;Jan&nbsp;2005</td>
<td>--</td>
<td>Announcement sent out after a majority of the mirrors have
received the bits.</td>
</tr>
<tr>
<td>Turn over to the secteam</td>
<td>--</td>
<td>--</td>
<td>RELENG_&local.rel.tag; branch is handed over to
the FreeBSD Security Officer Team in one or two weeks after the announcement.</td>
</tr>
</table>
<h1>Additional Information</h1>
<ul>
<li><a href="todo.html">FreeBSD &local.rel; developer todo list.</a></li>
<li><a href="qa.html">FreeBSD &local.rel; Quality Assurance Guide.</a></li>
<li><a href="&base;/releng/index.html">FreeBSD Release Engineering website.</a></li>
</ul>
&footer;
</body>
</html>

63
en/releases/4.11R/todo.sgml Normal file
View file

@ -0,0 +1,63 @@
<!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 title "FreeBSD &local.rel; Open Issues">
<!ENTITY % includes SYSTEM "../../includes.sgml"> %includes;
<!ENTITY % developers SYSTEM "../../developers.sgml"> %developers;
<!ENTITY status.na "<font color=green>N/A</font>">
<!ENTITY status.done "<font color=green>Done</font>">
<!ENTITY status.wip "<font color=blue>In&nbsp;progress</font>">
<!ENTITY status.untested "<font color=orange>Needs&nbsp;testing</font>">
<!ENTITY status.new "<font color=red>Not&nbsp;done</font>">
<!ENTITY status.unknown "<font color=red>Unknown</font>">
]>
<html>
&header;
<h1>Open Issues</h1>
<p>This is a list of open issues that need to be resolved for FreeBSD
&local.rel;. If you have any updates for this list, please e-mail
re@FreeBSD.org.</p>
<h3>Must Resolve Issues for &local.rel;-RC3</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
</table>
<h3>Must Resolve Issues for &local.rel;-RELEASE</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th>
</tr>
</table>
<h3>Desired Features for &local.rel;-RELEASE</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th></tr>
</table>
<h3>Documentation items that must be resolved for &local.rel;</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th></tr>
</table>
<h3>Testing focuses for &local.rel;</h3>
<table border=1 width="100%">
<tr><th>Issue</th><th>Status</th><th>Responsible</th><th>Description</th></tr>
</table>
&footer;
</body>
</html>