精華區beta FreeBSD 關於我們 聯絡資訊
FreeBSD 5.4 Release Process Introduction This is a specific schedule for the release of FreeBSD 5.4. For more general information about the release engineering process, please see the Release Engineering section of the web site. General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. MFC requests should be sent to [email protected]. Schedule +-----------------------------------------------------------------------------+ |Action |Expected|Actual|Description | |---------------------------+--------+------+---------------------------------| | | | |Release Engineers send | |Reminder announcement |31 Jan |31 Jan|announcement email to developers | | | | |with a rough schedule for the | | | | |FreeBSD 5.4 release. | |---------------------------+--------+------+---------------------------------| | | | |Someone from portmgr@ should | | | | |email freebsd-ports@ to set a | |Announce the Ports Freeze |-- |-- |date for the week long ports | | | | |freeze and tagging of the ports | | | | |tree. | |---------------------------+--------+------+---------------------------------| |5.4-PRERELEASE |23 Feb |-- |newvers.sh updated. | |---------------------------+--------+------+---------------------------------| | | | |After this date, all commits to | | | | |the RELENG_5 branch must be | | | | |approved by [email protected]. | | | | |Certain highly active | |Code freeze begins |2 Mar |-- |documentation committers are | | | | |exempt from this rule for routine| | | | |man page / release note updates. | | | | |Heads-up emails should be sent to| | | | |the developers, as well as | | | | |stable@ and qa@ lists. | |---------------------------+--------+------+---------------------------------| |5.4-PRERELEASE |4 Mar |-- |First public test release build. | |---------------------------+--------+------+---------------------------------| | | | |The release branch is created. | |RELENG_5_4 branch |16 Mar |-- |Update newvers.sh and release.ent| | | | |on various branches involved. | |---------------------------+--------+------+---------------------------------| | | | |Announcement to developers | | | | |explaining that commits to | |Unfreeze the tree |16 Mar |-- |RELENG_5 no longer require | | | | |approval. Also note the policy | | | | |for commits to the RELENG_5_4 | | | | |branch. | |---------------------------+--------+------+---------------------------------| |5.4-RC1 |16 Mar |-- |newvers.sh and release.ent | | | | |updated. | |---------------------------+--------+------+---------------------------------| | | | |The first release candidate for | | | | |the each architecture is | | | | |released. ISO images should be | | | | |uploaded to | | | | |ftp-master.FreeBSD.org. A network| | | | |install directory should be | | | | |uploaded to | | | | |ftp-master.FreeBSD.org. The | |First release candidate |18 Mar |-- |packages/ directory should be a | | | | |relative symlink, as described in| | | | |the releng article. When the | | | | |builds begin send a note to | | | | |[email protected] | | | | |saying a "Normal Release Cycle" | | | | |is beginning, RC ISOs and install| | | | |directories will be coming | | | | |through the next few weeks. | |---------------------------+--------+------+---------------------------------| | | | |A message should be sent to | |Heads up to -stable |18 Mar |-- |[email protected] and | | | | |[email protected] after the | | | | |first snapshot is uploaded. | |---------------------------+--------+------+---------------------------------| | | | |Note: the release date of this | |Second release candidate |25 Mar |-- |candidate depends on the user | | | | |experience with RC1. | |---------------------------+--------+------+---------------------------------| | | | |A message should be sent to | |Heads up to -stable |25 Mar |-- |[email protected] and | | | | |[email protected] after the | | | | |second snapshot is uploaded. | |---------------------------+--------+------+---------------------------------| | | | |Only approved commits will be | |Ports tree frozen |-- |-- |permitted to the ports/ tree | | | | |during the freeze. | |---------------------------+--------+------+---------------------------------| | | | |Notification of the impending doc| |Announce doc/ tree slush |-- |-- |/ tree slush should be sent to | | | | |doc@. | |---------------------------+--------+------+---------------------------------| | | | |Non-essential commits to the | | | | |en_US.ISO8859-1/ subtree should | |doc/ tree slush |-- |-- |be delayed from this point until | | | | |after the doc/ tree tagging, to | | | | |give translation teams time to | | | | |synchronize their work. | |---------------------------+--------+------+---------------------------------| |Ports tree tagged |-- |-- |RELEASE_5_4_0 tag for ports/. | |---------------------------+--------+------+---------------------------------| | | | |After the ports/ tree is tagged, | | | | |the ports/ tree will be re-opened| |Ports tree unfrozen |-- |-- |for commits, but commits made | | | | |after tagging will not go in | | | | |5.4-RELEASE. | |---------------------------+--------+------+---------------------------------| |Final package build starts |-- |-- |The ports cluster and pointyhat | | | | |build final packages. | |---------------------------+--------+------+---------------------------------| | | | |Version number bumps for doc/ | |doc/ tree tagged. |-- |-- |subtree. RELEASE_5_4_0 tag for | | | | |doc/. doc/ slush ends at this | | | | |time. | |---------------------------+--------+------+---------------------------------| | | | |The files listed here are updated| |Version numbers bumped. |30 Mar |-- |to reflect the fact that this is | | | | |FreeBSD 5.4. | |---------------------------+--------+------+---------------------------------| |src tree tagged. |30 Mar |-- |RELENG_5_4_0_RELEASE tag for src | | | | |/. | |---------------------------+--------+------+---------------------------------| | | | |Final builds for all | |Final builds. |30 Mar |-- |architectures in a pristine | | | | |environment. | |---------------------------+--------+------+---------------------------------| | | | |Heads up email to | | | | |[email protected] to | |Warn | | |give admins time to prepare for | |[email protected]|30 Mar |-- |the load spike to come. The site | | | | |administrators have frequently | | | | |requested advance notice for new | | | | |ISOs. | |---------------------------+--------+------+---------------------------------| | | | |Release uploaded to | | | | |ftp-master.FreeBSD.org (packages | |Upload to ftp-master. |2 Apr |-- |should have been done before now,| | | | |otherwise it chokes the mirror | | | | |sites and propagation of the | | | | |release bits takes too long) | |---------------------------+--------+------+---------------------------------| | | | |Make sure the 5.4 manual pages | |Update man.cgi on the | | |are being displayed by default | |website. |4 Apr |-- |for the man->web gateway. Also | | | | |make sure these man pages are | | | | |pointed to by docs.sgml. | |---------------------------+--------+------+---------------------------------| | | | |Announcement sent out after a | |Announcement |4 Apr |-- |majority of the mirrors have | | | | |received the bits. | |---------------------------+--------+------+---------------------------------| | | | |RELENG_5_4 branch is handed over | |Turn over to the secteam |11 Apr |-- |to the FreeBSD Security Officer | | | | |Team in one or two weeks after | | | | |the announcement. | +-----------------------------------------------------------------------------+ Additional Information * FreeBSD 5.4 developer todo list. * FreeBSD 5.4 Quality Assurance Guide. * FreeBSD Release Engineering website. ------------------------------------------------------------------------------- home | contact | legal | (C) 1995-2005 The FreeBSD Project. All rights reserved. Last modified: 2005/02/02 01:42:32 --