MFP4: FreeBSD 4.8 Release Schedule.
This commit is contained in:
Murray Stokely
parent
09fc5d1d0e
commit
df7d433519
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=15833
2 changed files with 300 additions and 0 deletions
14
en/releases/4.8R/Makefile
Normal file
14
en/releases/4.8R/Makefile
Normal file
|
|
@ -0,0 +1,14 @@
|
|||
# $FreeBSD$
|
||||
|
||||
.if exists(../Makefile.conf)
|
||||
.include "../Makefile.conf"
|
||||
.endif
|
||||
.if exists(../Makefile.inc)
|
||||
.include "../Makefile.inc"
|
||||
.endif
|
||||
|
||||
DOCS= schedule.sgml
|
||||
|
||||
DATA= docbook.css
|
||||
|
||||
.include "${WEB_PREFIX}/share/mk/web.site.mk"
|
||||
286
en/releases/4.8R/schedule.sgml
Normal file
286
en/releases/4.8R/schedule.sgml
Normal file
|
|
@ -0,0 +1,286 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||
<!ENTITY base CDATA "../..">
|
||||
<!ENTITY email 'freebsd-qa'>
|
||||
<!ENTITY date "$FreeBSD$">
|
||||
<!ENTITY local.rel "4.8">
|
||||
<!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>16 Jan 2003</td><td>16 Jan 2003</td>
|
||||
<td>Release Engineers send announcement email to
|
||||
developers@FreeBSD.org with a rough schedule for the FreeBSD
|
||||
&local.rel; release.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Another Reminder announcement</td><td>7 Feb 2003</td><td>--</td>
|
||||
<td>1 week reminder.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Another Reminder announcement</td><td>14 Feb 2003</td><td>--</td>
|
||||
<td>Final reminder, with exact time that freeze begins.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>&local.rel;-PRERELEASE Testing Guide published</td><td>15 Feb 2003</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><tt>&local.rel;-PRERELEASE</tt></td>
|
||||
<td>15 Feb 2003</td>
|
||||
<td>--</td>
|
||||
<td><tt>newvers.sh</tt>, and <tt>release.ent</tt> updated.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>FTP site updated</td>
|
||||
<td>15 Feb 2003</td>
|
||||
<td>--</td>
|
||||
<td><tt>pkg_add -r</tt> works for <tt>&local.rel;-PRERELEASE</tt> machines.</td>
|
||||
</tr>
|
||||
<tr>
|
||||
<td>Code freeze begins</td>
|
||||
<td>15 Feb 2003</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 developers@, stable@, and qa@ lists.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><tt>&local.rel;-RC</tt></td>
|
||||
<td>1 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td><tt>newvers.sh</tt> and <tt>release.ent</tt> updated.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Announce the Ports Freeze</td>
|
||||
<td>1 Mar 2003</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>First release candidate</td>
|
||||
<td>1 Mar 2003</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> and
|
||||
<tt>releng4.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.
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Heads up to -stable</td>
|
||||
<td>2 Feb 2003</td>
|
||||
<td>--</td>
|
||||
<td>A message should be sent to <tt>qa@FreeBSD.org</tt> and
|
||||
<tt>stable@FreeBSD.org</tt> after the snapshot is uploaded.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Second release candidate</td>
|
||||
<td>--</td>
|
||||
<td>--</td>
|
||||
<td>Note: the release date of this candidate depends on the user
|
||||
experience with RC1.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Third release candidate</td>
|
||||
<td>--</td>
|
||||
<td>--</td>
|
||||
<td></td>
|
||||
</tr>
|
||||
|
||||
<!-- portmgr should tweak these values after we commit it to CVS -->
|
||||
<tr>
|
||||
<td>Ports tree frozen</td>
|
||||
<td>5 Mar 2003</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>6 Mar 2003</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>10 Mar 2003</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 -->
|
||||
<tr>
|
||||
<td>Ports tree tagged</td>
|
||||
<td>13 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td><tt>RELEASE_4_8_0</tt> tag for <tt>ports/</tt>.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Ports tree unfrozen</td>
|
||||
<td>13 Mar 2003</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>14 Mar 2003</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>14 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>Version number bumps for <tt>doc/</tt> subtree.
|
||||
<tt>RELEASE_4_8_0</tt> tag for <tt>doc/</tt>. <tt>doc/</tt>
|
||||
slush ends at this time.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td><tt>RELENG_4_8</tt> branch</td>
|
||||
<td>13 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>The release branch is created.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Note to freebsd-stable@</td>
|
||||
<td>13 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>A note should be sent to the freebsd-stable@ list to let
|
||||
over-anxious users know that the tags have been created but the
|
||||
release still isn't ready. Tags may be slid before the
|
||||
announcement goes out. Point users to freebsd-qa@ for
|
||||
details.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Version numbers bumped.</td>
|
||||
<td>13 Mar 2003</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>Update man.cgi on the website.</td>
|
||||
<td>15 Mar 2003</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>src tree tagged.</td>
|
||||
<td>13 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td><tt>RELENG_4_8_0_RELEASE</tt> tag for src.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Final builds.</td>
|
||||
<td>13 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>Final builds for x86 and Alpha in a pristine environment.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Warn <tt>hubs@FreeBSD.org</tt></td>
|
||||
<td>13 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>Heads up email to <a
|
||||
href="mailto:hubs@FreeBSD.org">hubs@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>14 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>release and packages uploaded to <tt>ftp-master.FreeBSD.org</tt></td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Announcement</td>
|
||||
<td>17 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>Announcement sent out after a majority of the mirrors have
|
||||
received the bits.</td>
|
||||
</tr>
|
||||
|
||||
<tr>
|
||||
<td>Unfreeze the tree</td>
|
||||
<td>17 Mar 2003</td>
|
||||
<td>--</td>
|
||||
<td>Announcement to developers@ explaining that the release is
|
||||
out, and commits to RELENG_4 no longer require approval. Also
|
||||
note the policy for commits to the RELENG_4_8 branch.</td>
|
||||
</tr>
|
||||
|
||||
|
||||
</table>
|
||||
|
||||
&footer;
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Loading…
Reference in a new issue