diff --git a/en/releases/7.0R/schedule.sgml b/en/releases/7.0R/schedule.sgml index fff3054a32..3650140b90 100644 --- a/en/releases/7.0R/schedule.sgml +++ b/en/releases/7.0R/schedule.sgml @@ -1,181 +1,181 @@ - + ]> &header;

Introduction

This is a specific schedule for the release of FreeBSD &local.rel;. 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 re@FreeBSD.org.

Schedule

- +
Action Expected Actual Description
Reminder announcement TBD -- Release Engineers send announcement email to developers with a rough schedule for the FreeBSD &local.rel; release.
Announce the Ports Freeze TBD -- Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree.
Code freeze begins 18 June 2007 19 June 2007 After this date, all commits to HEAD must be approved by re@FreeBSD.org. 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, as well as stable@ and qa@ lists.
Announce doc/ tree slush TBD -- Notification of the impending doc/ tree slush should be sent to doc@.
Ports tree frozen TBD -- Only approved commits will be permitted to the ports/ tree during the freeze.
doc/ tree slush TBD -- Non-essential commits to the en_US.ISO8859-1/ subtree should be delayed from this point until after the doc/ tree tagging, to give translation teams time to synchronize their work.
doc/ tree tagged. TBD -- Version number bumps for doc/ subtree. RELEASE_&local.rel.tag;_0 tag for doc/. doc/ slush ends at this time.
RELENG_7 branchTBD --11 Oct 2007 The new major version branch is created. Update newvers.sh and release.ent on various branches involved.
RELENG_7_0 branch TBD -- The new release branch is created. Update newvers.sh and release.ent on various branches involved.
Ports tree tagged TBD -- RELEASE_&local.rel.tag;_0 tag for ports/.
Ports tree unfrozen TBD -- After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in &local.rel;-RELEASE.
Final package build starts TBD -- The ports cluster and pointyhat build final packages.
Announcement TBD -- Announcement sent out after a majority of the mirrors have received the bits.
Turn over to the secteam TBD -- RELENG_&local.rel.tag; branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement.

Additional Information

&footer; diff --git a/en/releng/index.sgml b/en/releng/index.sgml index 39433218ef..9746e25050 100644 --- a/en/releng/index.sgml +++ b/en/releng/index.sgml @@ -1,410 +1,419 @@ - + %developers; re@FreeBSD.org'> security-officer@FreeBSD.org'> portmgr@FreeBSD.org'> freebsd-doc@FreeBSD.org'> doceng@FreeBSD.org'> freebsd-www@FreeBSD.org'> ]> &header;

This page contains documentation about the FreeBSD release engineering process.

Upcoming Release Schedule

NOTE: Release dates are approximate and may be subject to schedule slippage.

Date Event Information
June 2007 Start FreeBSD 7.0 Release Process N/A
TBA Freeze RELENG_6 N/A
TBA Release FreeBSD 6.3 N/A

Code-Freeze Status

The following table lists the code freeze status for the major branches of the src/ subtree of the FreeBSD CVS repository. Commits to any branch listed as "frozen" must first be reviewed and approved by the relevant contact party. The status of other subtrees such as ports/, doc/, and www/ is also provided below.

+ + + + + + +
Branch Status Contact Notes
HEAD Frozen &contact.re; Active development branch for -CURRENT. Code-freeze in + preparation for 7.0-RELEASE. All commits must have &contact.re; + approval at this moment.
RELENG_7 Frozen &contact.re; Development branch for 7-STABLE. Code-freeze in preparation for 7.0-RELEASE. All commits must have &contact.re; approval until after the RELENG_7 branch has been created.
RELENG_6 Open &contact.re; Development branch for 6-STABLE.
RELENG_6_2 Frozen &contact.so; FreeBSD 6.2 supported errata fix branch.
RELENG_6_1 Frozen &contact.so; FreeBSD 6.1 supported errata fix branch.
RELENG_6_0 Frozen &contact.so; FreeBSD 6.0 errata fix branch (not officially supported).
RELENG_5 Open committers Development branch for 5-STABLE.
RELENG_5_5 Frozen &contact.so; FreeBSD 5.5 supported errata fix branch.
RELENG_5_4 Frozen &contact.so; FreeBSD 5.4 errata fix branch (not officially supported).
RELENG_5_3 Frozen &contact.so; FreeBSD 5.3 errata fix branch (not officially supported).
RELENG_5_2 Frozen &contact.so; FreeBSD 5.2 / 5.2.1 security fix branch (not officially supported).
RELENG_5_1 Frozen &contact.so; FreeBSD 5.1 security fix branch (not officially supported).
RELENG_5_0 Frozen &contact.so; FreeBSD 5.0 security fix branch (not officially supported).
RELENG_4 Open committers Maintenance branch for 4-STABLE (not officially supported).
RELENG_4_11 Frozen &contact.so; FreeBSD 4.11 errata fix branch (not officially supported).
RELENG_4_10 Frozen &contact.so; FreeBSD 4.10 security fix branch (not officially supported).
RELENG_4_9 Frozen &contact.so; FreeBSD 4.9 security fix branch (not officially supported).
RELENG_4_8 Frozen &contact.so; FreeBSD 4.8 security fix branch (not officially supported).
RELENG_4_7 Frozen &contact.so; FreeBSD 4.7 security fix branch (not officially supported).
RELENG_4_6 Frozen &contact.so; FreeBSD 4.6 security fix branch (not officially supported).
RELENG_4_5 Frozen &contact.so; FreeBSD 4.5 security fix branch (not officially supported).
RELENG_4_4 Frozen &contact.so; FreeBSD 4.4 security fix branch (not officially supported).
RELENG_4_3 Frozen &contact.so; FreeBSD 4.3 security fix branch (not officially supported).
RELENG_3 Open committers Maintenance branch for 3-STABLE (not officially supported).
RELENG_2_2 Open committers Maintenance branch for 2.2-STABLE (not officially supported).
Subtree Status Contact Notes
ports/ Open freebsd-ports FreeBSD Ports Collection.
doc/ Open &contact.doc; SGML/XML based documentation set.
www/ Open &contact.www; FreeBSD Web site sources.

Release Engineering Documentation

Release Engineering Team

The primary release engineering team is responsible for approving MFC requests during code freezes, setting release schedules, and all of the other responsibilities laid out in our charter.

Primary RE Team (re@FreeBSD.org) : &a.re.members; form the primary release engineering decision-making group.

The platform-specific release engineering teams are responsible for building and packaging FreeBSD releases on the given platforms.

Alpha Platform REs (re-alpha@FreeBSD.org) : &a.re-alpha;

AMD64 Platform REs (re-amd64@FreeBSD.org) : &a.re-amd64;

ia64 Platform REs (re-ia64@FreeBSD.org) : &a.re-ia64;

i386 Platform REs (re-x86@FreeBSD.org) : &a.re-i386;

pc98 Platform REs (re-pc98@FreeBSD.org) : &a.re-pc98;

PowerPC Platform REs (re-ppc@FreeBSD.org) : &a.re-powerpc;

sparc64 Platform REs (re-sparc64@FreeBSD.org) : &a.re-sparc64;

The third party packages in the Ports Collection are managed by the portmgr@ team. Among many other responsibilities, the port managers keep the ports cluster running smoothly to produce binary packages.

Package Builders (&contact.portmgr;) : &a.portmgr;

Frequently Asked Questions

Where can I find the release directory or ISO images for older FreeBSD releases?

The FreeBSD Project does not maintain a centralized historical archive of old release ISO images, but there are still many options. First, a large collection of the old releases (many complete with the package sets) is at ftp://ftp-archive.FreeBSD.org/pub/FreeBSD-Archive/old-releases/. Second, try looking on http://mirrorlist.FreeBSD.org. If you are unable to find an FTP mirror that still contains the release you are looking for, then you can email CD-ROM vendors to see if they have any old releases available. In September 2003, we know of a case where FreeBSD 1.1 was used in a court of law to invalidate a bogus software patent. Clearly, older releases can be very important in some situations.

&footer;