The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.10-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 4.10-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in 4.10-RELEASE that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:
To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.
The release notes will always be +
The release notes will always be a good place to look for things to test.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.10-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 4.10. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
| Reminder announcement | 30 Mar 2004 | 30 Mar 2004 | Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.10 release. | |
| 4.10-BETA Testing Guide published | 30 Mar 2004 | 30 Mar 2004 | -A testing guide + | A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period. |
| Announce the Ports Freeze | 03 Apr 2004 | 03 Apr 2004 | Someone from portmgr@ should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| 4.10-BETA | 7 Apr 2004 | 10 Apr 2004 | newvers.sh, and release.ent updated. | |
| Code freeze begins | 7 Apr 2004 | 7 Apr 2004 | After this date, all commits to the RELENG_4 branch 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@, stable@ and qa@ lists. | |
| RELENG_4_10 branch | 20 Apr 2004 | 21 Apr 2004 | The release branch is created. | |
| Unfreeze the tree | 20 Apr 2004 | 22 Apr 2004 | Announcement to developers@ explaining that commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_4_10 branch. | |
| 4.10-RC | 20 Apr 2004 | 24 Apr 2004 | newvers.sh and release.ent updated. | |
| First release candidate | 21 Apr 2004 | 22 Apr 2004 | The first release candidate for the x86 and Alpha 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 packages/ directory should be a relative symlink, as described in the releng article. When the builds begin send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks. | |
| Heads up to -stable | 21 Apr 2004 | 23 Apr 2004 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded. | |
| Second release candidate | 27 Apr 2004 | 2 May 2004 | Note: the release date of this candidate depends on the user experience with RC1. | |
| Heads up to -stable | 28 Apr 2004 | 3 May 2004 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded. | |
| Third release candidate | -- | 17 May 2004 | Note: the release date of this candidate depends on the user experience with RC2. | |
| Heads up to -stable | -- | 17 May 2004 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded. | |
| Ports tree frozen | 20 Apr 2004 | 20 Apr 2004 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Announce doc/ tree slush | -- | 12 Apr 2004 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| doc/ tree slush | 17 Apr 2004 | 17 Apr 2004 | 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. | |
| Ports tree tagged | 27 Apr 2004 | 28 Apr 2004 | RELEASE_4_10_0 tag for ports/. | |
| Ports tree unfrozen | 27 Apr 2004 | 28 Apr 2004 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.10-RELEASE. | |
| Final package build starts | -- | -- | The ports cluster and bento build final packages. | |
| doc/ tree tagged. | 24 Apr 2004 | 24 Apr 2004 | Version number bumps for doc/ subtree. RELEASE_4_10_0 tag for doc/. doc/ slush ends at this time. | |
| Version numbers bumped. | 22 May 2004 |
24 May 2004 | -The files listed here + | The files listed here are updated to reflect the fact that this is FreeBSD 4.10. |
| Update man.cgi on the website. | 22 May 2004 |
25 May 2004 | Make sure the 4.10 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml. | |
| src tree tagged. | 22 May 2004 |
25 May 2004 | RELENG_4_10_0_RELEASE tag for src/. | |
| Final builds. | 22 May 2004 |
26 May 2004 | Final builds for x86 and Alpha in a pristine environment. | |
| Warn mirror-announce@FreeBSD.org | 23 May 2004 |
25 May 2004 | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master. | 23 May 2004 |
26 May 2004 | Release uploaded to ftp-master.FreeBSD.org (packages should have been done before now, otherwise it chokes the mirror sites and propagation of the release bits takes too long) | |
| Announcement | 24 May 2004 |
27 May 2004 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to the secteam | -- | 3 June 2004 | RELENG_4_10 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
This is a list of open issues that need to be resolved for FreeBSD 4.10. If you have any updates for this list, please e-mail re@FreeBSD.org.
As many of these open issues involve merging bus_dma driver changes - from -CURRENT, the busdma project page is + from -CURRENT, the busdma project page is also useful.
| Issue | Status | Responsible | Description |
|---|
| Issue | Status | Responsible | Description |
|---|
| Issue | Status | Responsible | Description |
|---|
| Issue | Status | Responsible | Description |
|---|
| Issue | Status | Responsible | Description |
|---|---|---|---|
| twe(4) stability problem | Needs testing | -- | The twe(4) driver has a stability problem when a lot of rapid sequential small file inserts into a new directory tree. A set of patches for the problem has been committed just before 4.10-RC3. |
| vmspace leak | Needs testing | -- | Copying vm_exitingcnt to the new vmspace in vmspace_exec() can make it very high values and never drop to 0 and be freed. This can cause a system crash. A patch for the problem has been committed just before 4.10-RC3. |
| twa(4) fails in sysinstall | Needs testing | -- | When a twa(4) device in a system with no SCSI controller is detected, sysinstall in 4.10-RC2 does not recognize the disks attached. It seems that this problem may involve inconsistency between the CAM device rescanning and the kernel module loading. A patch for the problem has been committed just before 4.10-RC3. |
The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.11-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 4.11-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.11-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 4.11. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
| Reminder announcement | 30 Nov 2004 | 30 Nov 2004 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 4.11 release. | |
| 4.11-BETA Testing Guide published | -- | -- | -A testing guide + | A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period. |
| Announce the Ports Freeze | -- | 18 Dec 2004 | Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| 4.11-PRERELEASE | 6 Dec 2004 | 6 Dec 2004 | newvers.sh updated. | |
| Code freeze begins | 13 Dec 2004 | 13 Dec 2004 | After this date, all commits to the RELENG_4 branch 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. | |
| RELENG_4_11 branch | 17 Dec 2004 | 17 Dec 2004 | The release branch is created. Update newvers.sh and release.ent on various branches involved. | |
| Unfreeze the tree | 17 Dec 2004 | 17 Dec 2004 | Announcement to developers explaining that commits to RELENG_4 no longer require approval. Also note the policy for commits to the RELENG_4_11 branch. | |
| 4.11-RC | 17 Dec 2004 | 17 Dec 2004 | newvers.sh and release.ent updated. | |
| First release candidate | 20 Dec 2004 | 18 Dec 2004 | The first release candidate for the x86 and Alpha 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 packages/ directory should be a relative symlink, as described in the releng article. When the builds begin send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks. | |
| Heads up to -stable | 20 Dec 2004 | 18 Dec 2004 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded. | |
| Second release candidate | 3 Jan 2005 | 3 Jan 2005 | Note: the release date of this candidate depends on the user experience with RC1. | |
| Heads up to -stable | 3 Jan 2005 | 3 Jan 2005 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded. | |
| Third release candidate | 17 Jan 2005 | 17 Jan 2005 | Note: the release date of this candidate depends on the user experience with RC2. | |
| Heads up to -stable | 17 Jan 2005 | 17 Jan 2005 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded. | |
| Ports tree frozen | 30 Dec 2004 | 31 Dec 2004 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Announce doc/ tree slush | 27 Dec 2004 | 29 Dec 2004 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| doc/ tree slush | 14 Jan 2005 | 15 Jan 2005 | 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. | |
| Ports tree tagged | 6 Jan 2005 | 8 Jan 2005 | RELEASE_4_11_0 tag for ports/. | |
| Ports tree unfrozen | 7 Jan 2005 | 8 Jan 2005 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.11-RELEASE. | |
| Final package build starts | 6 Jan 2005 | -- | The ports cluster and pointyhat build final packages. | |
| doc/ tree tagged. | 18 Jan 2005 | -- | Version number bumps for doc/ subtree. RELEASE_4_11_0 tag for doc/. doc/ slush ends at this time. | |
| Version numbers bumped. | 20 Jan 2005 | 21 Jan 2005 | -The files listed here + | The files listed here are updated to reflect the fact that this is FreeBSD 4.11. |
| src tree tagged. | 20 Jan 2005 | 21 Jan 2005 | RELENG_4_11_0_RELEASE tag for src/. | |
| Final builds. | 20 Jan 2005 | 21 Jan 2005 | Final builds for x86 and Alpha in a pristine environment. | |
| Warn mirror-announce@FreeBSD.org | 21 Jan 2005 | 24 Jan 2005 | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master. | 22 Jan 2005 | 24 Jan 2005 | Release uploaded to ftp-master.FreeBSD.org (packages should have been done before now, otherwise it chokes the mirror sites and propagation of the release bits takes too long) | |
| Update man.cgi on the website. | 24 Jan 2005 | 25 Jan 2005 | Make sure the 4.11 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml. | |
| Announcement | 24 Jan 2005 | 25 Jan 2005 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to the secteam | 2 Feb 2005 | 1 Feb 2005 | RELENG_4_11 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.4 are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.4 are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The FreeBSD Project now releases the full 4-CDROM set formerly produced by Walnut Creek CDROM / BSDi. This CDROM set may be replicated by vendors wishing to sell "Official" copies of FreeBSD.
4.5-install.iso - This is a bootable CDROM image that contains the base system, XFree86 3.3.6, a 'tools' directory of software for users performing an installation from other - operating systems, and 2,210 third-party software packages. [ file + operating systems, and 2,210 third-party software packages. [ file listing ]
4.5-disc2.iso - This is a bootable CDROM that may be used as a live filesystem disc. This disc also contains a compressed copy of the CVS repository in the CVS-REPO directory, and some commercial software demos for FreeBSD in the - commerce directory. [ file + commerce directory. [ file listing ]
4.5-disc3.iso, 4.5-disc4.iso - The remaining two discs contain the most popular third-party software package - that users have requested. [ Disc 3 listing ] [ Disc 4 listing ]
+ that users have requested. [ Disc 3 listing ] [ Disc 4 listing ]The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.5 are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.5 are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in 4.5-PRERELEASE that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:
To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.
The release notes will always be +
The release notes will always be a good place to look for things to test. There are a number of new drivers, including if_em, which would probably benefit from more exposure. Please report bugs to the qa@FreeBSD.org list, and/or via send-pr with a heads up to the qa list.
4.5 Release Candidate 3 was released on January 23. There will be one final release candidate before the final release. Please see the postings to qa@FreeBSD.org and stable@FreeBSD.org for more information.
The release engineering team (re@FreeBSD.org) for FreeBSD 4.5 consists of Murray Stokely, Steve Price, Robert Watson, and John Baldwin.
The x86 build team consists of Murray Stokely and John Baldwin.
The Alpha build team consists of David O'Brien, Wilko Bulte, John Baldwin, and Murray Stokely.
The third-party packages are handled by Steve Price and the Ports managers (portmgr@FreeBSD.org).
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.
For an overview of the entire release engineering process, please - see this + see this document.
| Action | Expected | Actual | Description |
| Reminder announcement | 01 Dec 2001 | 03 Dec 2001 | Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.5 release. |
| 4.5-PRERELEASE | 20 Dec 2001 | 20 Dec 2001 | newvers.sh, param.h, and release.ent updated. |
| FTP site updated | 20 Dec 2001 | 20 Dec 2001 | pkg_add -r works for 4.5-PRERELEASE machines. |
| Code freeze begins | 20 Dec 2001 | 20 Dec 2001 | After this date, all commits to the RELENG_4 branch 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@, stable@, and qa@ lists. |
| Commercial software demos updated. | 05 Jan 2002 | 24 Jan 2002 | The second disc contains commercial software demos, these demos should be updated to contain the latest versions. |
| 4.5-RC | 09 Jan 2002 | 09 Jan 2002 | newvers.sh and release.ent updated. |
| Announce the Ports Freeze | 09 Jan 2002 | 09 Jan 2002 | Someone from portmgr should email freebsd-ports@ and CC: developers@ to set a date for the tagging of the ports tree. Will set this date at January 22nd. |
| Heads up to hubs | 09 Jan 2002 | 09 Jan 2002 | A message should be sent to freebsd-hubs@FreeBSD.org before the release is uploaded. The site administrators have frequently requested advance notice for new ISOs. |
| First release candidate | 09 Jan 2002 | 09 Jan 2002 | The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages and XF86336 directories may be symlinked to save space, as long as you're sure to use relative symlinks. |
| Heads up to -stable | 09 Jan 2002 | 09 Jan 2002 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the release is uploaded. |
| Second release candidate | ?? Jan 2002 | 18 Jan 2002 | Note: the release date of this candidate depends on the user experience with RC1. |
| Third release candidate | 23 Jan 2002 | 24 Jan 2002 | 4.5 RC3 for the x86 and Alpha architectures will be made available from ftp.FreeBSD.org and the mirrors. |
| Ports tree frozen. | 22 Jan 2002 | 22 Jan 2002 | CVSROOT/avail locks out everyone but the person who does the tagging. It will take approximately 2 hours to tag the entire ports tree with the RELEASE_4_5_0 tag. After this time, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.5-RELEASE. |
| Final package build starts | 22 Jan 2002 | 22 Jan 2002 | The ports cluster and bento build final packages. |
| Package split | 23 Jan 2002 | 29 Jan 2002 | The packages must be split so that packages with similar dependencies appear on each of the four discs, with the most popular packages appearing on the first disc. |
| doc tree tagged. | 24 Jan 2002 | 24 Jan 2002 | RELEASE_4_5_0 tag for docs. |
| RELENG_4_5 branch | 25 Jan 2002 | 26 Jan 2002 | The release branch is created. |
| Note to freebsd-stable@ | 25 Jan 2002 | 26 Jan 2002 | A note should be sent to the freebsd-stable 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. |
| Version numbers bumped. | 25 Jan 2002 | 25 Jan 2002 | The files listed here are updated to reflect the fact that this is FreeBSD 4.5. |
| src tree tagged. | 27 Jan 2002 | 27 Jan 2002 | RELEASE_4_5_0_RELEASE tag for src. |
| Update man.cgi on the website. | 25 Jan 2002 | -- | Make sure the 4.5 manual pages are being displayed by default for the man->web gateway. |
| Archive the errata for FreeBSD 4.4. | 25 Jan 2002 | 25 Jan 2002 | The new RELNOTESng errata file should be setup, and the old errata file archived. |
| Final builds. | 28 Jan 2002 | 28 Jan 2002 | Final builds for x86 and Alpha in a pristine environment. |
| Warn hubs@FreeBSD.org | 28 Jan 2002 | 28 Jan 2002 | Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. |
| Upload to ftp-master. | 28 Jan 2002 | 28 Jan 2002 | release and packages uploaded to ftp-master.FreeBSD.org |
| Announcement | 28 Jan 2002 | 29 Jan 2002 | Announcement sent out after a majority of the mirrors have received the bits. |
It's been pointed out that this table is rather boring. Bruce Mah gave a slightly more interesting rendition of the 12 days of Code-Freeze.
The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.6.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.6.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The FreeBSD Project now releases the full 4-CDROM set formerly produced by Walnut Creek CDROM / BSDi. This CDROM set may be replicated by vendors wishing to sell "Official" copies of FreeBSD.
4.6-disc1.iso - This is a bootable CDROM image that contains the base system, XFree86 4.2.0, a 'tools' directory of software for users performing an installation from other - operating systems, and 2,131 third-party software packages. [ file + operating systems, and 2,131 third-party software packages. [ file listing ]
4.6-disc2.iso - This is a bootable CDROM that may be used as a live filesystem disc. This disc also contains a compressed copy of the CVS repository in the CVS-REPO directory, and some commercial software demos for FreeBSD in the - commerce directory. [ file + commerce directory. [ file listing ]
4.6-disc3.iso, 4.6-disc4.iso - The remaining two discs contain the most popular third-party software package that users have requested. They contain 2,399 and 550 packages, - respectively.[ Disc 3 listing ] [ Disc 4 listing ]
+ respectively.[ Disc 3 listing ] [ Disc 4 listing ]The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.6-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 4.6-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in 4.6-PRERELEASE that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:
To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.
The release notes will always be +
The release notes will always be a good place to look for things to test.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.6-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 4.6. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
| Reminder announcement | 01 Apr 2002 | 09 Apr 2002 | Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.6 release. | |
| 4.6-PRERELEASE Testing Guide published | Ongoing | -- | -A testing guide + | A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period. |
| 4.6-PRERELEASE | 01 May 2002 | 01 May 2002 | newvers.sh, and release.ent updated. | |
| FTP site updated | 01 May 2002 | 18 May 2002 | pkg_add -r works for 4.6-PRERELEASE machines. | |
| Code freeze begins | 01 May 2002 | 01 May 2002 | After this date, all commits to the RELENG_4 branch 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@, stable@ and qa@ lists. | |
| Commercial software demos updated. | 15 May 2002 | -- | The second disc contains commercial software demos, these demos should be updated to contain the latest versions. | |
| 4.6-RC | 15 May 2002 | 15 May 2002 | newvers.sh and release.ent updated. | |
| Announce the Ports Freeze | 15 May 2002 | 19 May 2002 | Someone from portmgr should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| Heads up to hubs | 28 May 2002 | -- | A message should be sent to freebsd-hubs@FreeBSD.org before the release is uploaded. The site administrators have frequently requested advance notice for new ISOs. | |
| First release candidate | 16 May 2002 | 17 May 2002 | The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ and XF86336/ directories may be symlinked to save space, as long as you're sure to use relative symlinks. | |
| Heads up to -stable | 17 May 2002 | 17 May 2002 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded. | |
| Package split posted | 17 May 2002 | -- | The proposed package split (which packages go on which disc of the 4 CD set) should be posted to qa@FreeBSD.org, ports@FreeBSD.org, and stable@FreeBSD.org. | |
| Second release candidate | ?? May 2002 | 18 May 2002 | Note: the release date of this candidate depends on the user experience with RC1. | |
| Third release candidate | -- | -- | There will be no 4.6 RC3 snapshot. | |
| Ports tree frozen. | 24 May 2002 | 25 May 2002 | CVSROOT/avail locks out everyone but the person who does the tagging. It will take approximately 2 hours to tag the entire ports tree with the RELEASE_4_6_0 tag. After this time, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.6-RELEASE. | |
| Final package build starts | 25 May 2002 | -- | The ports cluster and bento build final packages. | |
| Package split | 26 May 2002 | -- | The packages must be split so that packages with similar dependencies appear on each of the four discs, with the most popular packages appearing on the first disc. | |
| doc/ tree tagged. | 27 May 2002 | 27 May 2002 | RELEASE_4_6_0 tag for docs. | |
| Fourth release candidate | 3 June 2002 | 6 June 2002 | 4.6 RC4 for the x86 and Alpha architectures will be made available from ftp.FreeBSD.org and the mirrors. | |
| RELENG_4_6 branch | 5 June 2002 | 6 June 2002 | The release branch is created. | |
| Note to freebsd-stable@ | 5 June 2002 | 6 June 2002 | A note should be sent to the freebsd-stable@ 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. | |
| Version numbers bumped. | 5 June 2002 | 8 June 2002 | -The files listed here + | The files listed here are updated to reflect the fact that this is FreeBSD 4.6. |
| Update man.cgi on the website. | 6 June 2002 | 3 June 2002 | Make sure the 4.6 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml. | |
| src tree tagged. | 10 June 2002 | 10 June 2002 | RELENG_4_6_0_RELEASE tag for src. | |
| Final builds. | 10 June 2002 | -- | Final builds for x86 and Alpha in a pristine environment. | |
| Warn hubs@FreeBSD.org | 10 June 2002 | 11 June 2002 | Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. | |
| Upload to ftp-master. | 10 June 2002 | 14 June 2002 | release and packages uploaded to ftp-master.FreeBSD.org | |
| Announcement | 10 Jun 2002 | 15 June 2002 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Unfreeze the tree | 10 June 2002 | 16 June | 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_6 branch. |
The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.7-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 4.7-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in 4.7-RELEASE that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:
To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.
PPP. A number of significant PPP changes were merged to -STABLE before the code freeze. In particular, the following changes were made:
The release notes will always be +
The release notes will always be a good place to look for things to test.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.7-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 4.7. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
| Reminder announcement | 06 Aug 2002 | 06 Aug 2002 | Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.7 release. | |
| 4.7-PRERELEASE Testing Guide published | Ongoing | 02 Sep 2002 | -A testing guide + | A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period. |
| 4.7-PRERELEASE | 01 Sep 2002 | 02 Sep 2002 | newvers.sh, and release.ent updated. | |
| FTP site updated | 01 Sep 2002 | 02 Sep 2002 | pkg_add -r works for 4.7-PRERELEASE machines. | |
| Code freeze begins | 01 Sep 2002 | 01 Sep 2002 | After this date, all commits to the RELENG_4 branch 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@, stable@, and qa@ lists. | |
| Commercial software demos updated. | -- | -- | The second disc contains commercial software demos, these demos should be updated to contain the latest versions. | |
| 4.7-RC | 15 Sep 2002 | 16 Sep 2002 | newvers.sh and release.ent updated. | |
| Announce the Ports Freeze | 15 Sep 2002 | 16 Sep 2002 | Someone from portmgr should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| First release candidate | 15 Sep 2002 | 18 Sep 2002 | The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages directory should be a relative symlink, as described in the releng article. | |
| Heads up to -stable | 17 Sep 2002 | 18 Sep 2002 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded. | |
| Package split posted | 17 Sep 2002 | -- | The proposed package split (which packages go on which disc of the 4 CD set) should be posted to qa@FreeBSD.org, ports@FreeBSD.org, and stable@FreeBSD.org. | |
| Second release candidate | -- | 27 Sep 2002 | Note: the release date of this candidate depends on the user experience with RC1. | |
| Third release candidate | -- | 07 Oct 2002 | ||
| Ports tree frozen | 20 Sep 2002 | 21 Sep 2002 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Ports tree tagged | 24 Sep 2002 | 01 Oct 2002 | RELEASE_4_7_0 tag for ports/. | |
| Ports tree unfrozen | 24 Sep 2002 | 05 Oct 2002 | After the ports tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.7-RELEASE. | |
| Final package build starts | 25 Sep 2002 | 05 Oct 2002 | The ports cluster and bento build final packages. | |
| Package split | 26 Sep 2002 | 08 Oct 2002 | The packages must be split so that packages with similar dependencies appear on each of the four discs, with the most popular packages appearing on the first disc. | |
| doc tree tagged. | 27 Sep 2002 | 01 Oct 2002 | RELEASE_4_7_0 tag for docs. | |
| RELENG_4_7 branch | 28 Sep 2002 | 06 Oct 2002 | The release branch is created. | |
| Note to freebsd-stable@ | 28 Sep 2002 | 06 Oct 2002 | 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. | |
| Version numbers bumped. | 29 Sep 2002 | 07 Oct 2002 | -The files listed here + | The files listed here are updated to reflect the fact that this is FreeBSD 4.7. |
| Update man.cgi on the website. | 29 Sep 2002 | 06 Oct 2002 | Make sure the 4.7 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml. | |
| src tree tagged. | 29 Sep 2002 | 06 Oct 2002 | RELENG_4_7_0_RELEASE tag for src. | |
| Final builds. | 08 Oct 2002 | 08 Oct 2002 | Final builds for x86 and Alpha in a pristine environment. | |
| Warn hubs@FreeBSD.org | 30 Sep 2002 | 09 Oct 2002 | Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master. | 08 Oct 2002 | 09 Oct 2002 | release and packages uploaded to ftp-master.FreeBSD.org | |
| Announcement | 08 Oct 2002 | 10 Oct 2002 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Unfreeze the tree | 08 Oct 2002 | 10 Oct 2002 | 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_7 branch. |
The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.8-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 4.8-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in 4.8-RELEASE that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:
To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.
OpenSSL. OpenSSL was updated to 0.9.7a. Please test any SSL consumers on your system to make sure there have been no regressions in functionality.
IPFilter has recently been updated to version 3.4.31 and has not yet been thoroughly tested in -STABLE.
Firewire
libc_r - A change has been made to fix libc_r in the case when a non-standard value of KVA_PAGES is used in the kernel. libc_r in general could use testing with real applications.
dlinfo() added - test your shared-library heavy ports to make sure there are no build problems.
ISC DHCP 3.0.1 RC11 has recently been added to 4.8RC. This version of the ISC DHCP client was used in 5.0-RELEASE, and should be well tested, but it was only recently made available to 4.X-STABLE users so it has not received much testing to date in that environment.
The release notes will always be +
The release notes will always be a good place to look for things to test.
Disks attached to a Mylex controller are not seen by sysinstall. There is a problem because this module is loaded from the mfsroot floppy and the equivalent of a "camcontrol rescan" is not performed to discover disks after the module has loaded. Found by Julian. Fixed by scottl Mar 28.
GNOME2 does not work until the user manually runs 'fc-cache -f'. marcus@ has committed a fix to the port, murray@ has manually hacked some packages to test the proposed fixes, and kris@ will rebuild 150+ GNOME ports
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.8-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 4.8. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
| Reminder announcement | 16 Jan 2003 | 16 Jan 2003 | Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.8 release. | |
| Another Reminder announcement | 7 Feb 2003 | 10 Feb 2003 | 1 week reminder. | |
| Another Reminder announcement | 14 Feb 2003 | 14 Feb 2003 | Final reminder, with exact time that freeze begins. | |
| 4.8-PRERELEASE Testing Guide published | 15 Feb 2003 | 2 Mar 2003 | -A testing guide + | A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period. |
| 4.8-PRERELEASE | 15 Feb 2003 | 15 Feb 2003 | newvers.sh, and release.ent updated. | |
| FTP site updated | 15 Feb 2003 | unnecessary | pkg_add -r works for 4.8-PRERELEASE machines. | |
| Code freeze begins | 15 Feb 2003 | 15 Feb 2003 | After this date, all commits to the RELENG_4 branch 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@, stable@ and qa@ lists. | |
| 4.8-RC | 1 Mar 2003 | 2 Mar 2003 | newvers.sh and release.ent updated. | |
| Announce the Ports Freeze | 1 Mar 2003 | 1 Mar 2003 | Someone from portmgr@ should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| First release candidate | 1 Mar 2003 | 3 Mar 2003 | The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ directory should be a relative symlink, as described in the releng article. | |
| Heads up to -stable | 2 Mar 2003 | 3 Mar 2003 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded. | |
| Second release candidate | 16 Mar 2003 | 17 Mar 2003 | Note: the release date of this candidate depends on the user experience with RC1. | |
| Third release candidate | -- | -- | ||
| Ports tree frozen | 5 Mar 2003 | 6 Mar 2003 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Announce doc/ tree slush | 6 Mar 2003 | 7 Mar 2003 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| doc/ tree slush | 10 Mar 2003 | 10 Mar 2003 | 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. | |
| Ports tree tagged | 13 Mar 2003 | -- | RELEASE_4_8_0 tag for ports/. | |
| Ports tree unfrozen | 22 Mar 2003 | 22 Mar 2003 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.8-RELEASE. | |
| Final package build starts | 20 Mar 2003 | -- | The ports cluster and bento build final packages. | |
| doc/ tree tagged. | 19 Mar 2003 | 22 Mar 2003 | Version number bumps for doc/ subtree. RELEASE_4_8_0 tag for doc/. doc/ slush ends at this time. | |
| RELENG_4_8 branch | 22 Mar 2003 | 23 Mar 2003 | The release branch is created. | |
| Note to freebsd-stable@ | 22 Mar 2003 | -- | 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. | |
| Version numbers bumped. | 23 Mar 2003 | -- | -The files listed here + | The files listed here are updated to reflect the fact that this is FreeBSD 4.8. |
| Update man.cgi on the website. | 23 Mar 2003 | 28 Mar 2003 | Make sure the 4.8 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml. | |
| src tree tagged. | 29 Mar 2003 | -- | RELENG_4_8_0_RELEASE tag for src/. | |
| Final builds. | 29 Mar 2003 | -- | Final builds for x86 and Alpha in a pristine environment. | |
| Warn hubs@FreeBSD.org | 29 Mar 2003 | -- | Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master. | 29 Mar 2003 | -- | Release and packages uploaded to ftp-master.FreeBSD.org | |
| Announcement | 30 Mar 2003 | -- | Announcement sent out after a majority of the mirrors have received the bits. | |
| Unfreeze the tree | 30 Mar 2003 | -- | 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. |
The hardware notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Hardware notes for FreeBSD 4.9-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 4.9-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
As part of our on-going effort to improve the release engineering process, we have identified several areas that need significant quality assurance testing during the release candidate phase. Below, we've listed the changes in 4.9-RELEASE that we feel merit the most attention due to their involving substantial changes to the system, or having arrived late in the development cycle leading up to the release. In general, our goal in the QA process is to attempt to check a number of things:
To effectively determine this, it's desirable to test the system in a diverse set of environments, applying a wide set of workloads, forcing the system to operate both within and outside its normal specification. Particular focus should often be placed on the continuing (or new) capability of the system to perform correctly when used in concert with systems from other vendors.
A bug affecting IPFW2 "limit" rules was fixed very late in the release cycle; other ipfw2 features should not be affected. We are interested in hearing any feedback about IFPW2 in 4.9-RC3.
The sysinstall(8) utility was updated to support multiple mail transfer agents (MTAs). As such, the familiar Network Services menu was modified to expose a new option entitled Mail.
The xl driver has recently been updated with full busdma support among other improvements. This driver will now work with large memory systems with PAE enabled.
Users with large memory configurations (>4G) should explore the recently added PAE support in 4.9-RELEASE.
The release notes will always be +
The release notes will always be a good place to look for things to test.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 4.9-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 4.9. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
| Reminder announcement | 28 Jul 2003 | 28 Jul 2003 | Release Engineers send announcement email to developers@FreeBSD.org with a rough schedule for the FreeBSD 4.9 release. | |
| Another Reminder announcement | 18 Aug 2003 | 18 Aug 2003 | 1 week reminder. | |
| Another Reminder announcement | 24 Aug 2003 | 24 Aug 2003 | Final reminder, with exact time (GMT) that freeze begins. | |
| 4.9-PRERELEASE Testing Guide published | 25 Aug 2003 | -- | -A testing guide + | A testing guide should be published with information about recent changes and areas of the system that should be thoroughly tested during the pre-release/RC period. |
| 4.9-PRERELEASE | 25 Aug 2003 | 25 Aug 2003 | newvers.sh, and release.ent updated. | |
| FTP site updated | 25 Aug 2003 | 25 Aug 2003 | pkg_add -r works for 4.9-PRERELEASE machines. | |
| Code freeze begins | 25 Aug 2003 | 25 Aug 2003 | After this date, all commits to the RELENG_4 branch 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@, stable@ and qa@ lists. | |
| 4.9-RC | 12 Sep 2003 | 28 Sep 2003 | newvers.sh and release.ent updated. | |
| Announce the Ports Freeze | 19 Aug 2003 | 19 Aug 2003 | Someone from portmgr@ should email freebsd-ports@ and BCC: developers@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| First release candidate | 12 Sep 2003 | 28 Sep 2003 | The first release candidate for the x86 and Alpha architecture is released. ISO images should be uploaded to ftp-master.FreeBSD.org and releng4.FreeBSD.org. A network install directory should be uploaded to ftp-master.FreeBSD.org. The packages/ directory should be a relative symlink, as described in the releng article. Send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks. | |
| Heads up to -stable | 12 Sep 2003 | 28 Sep 2003 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the snapshot is uploaded. | |
| Second release candidate | 17 Sep 2003 | 8 Oct 2003 | Note: the release date of this candidate depends on the user experience with RC1. | |
| Third release candidate | 17 Oct 2003 | 18 Oct 2003 | ||
| Ports tree frozen | 10 Sep 2003 | 10 Sep 2003 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Announce doc/ tree slush | 17 Oct 2003 | 18 Oct 2003 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| doc/ tree slush | 18 Oct 2003 | 18 Oct 2003 | 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. | |
| Ports tree tagged | 23 Sep 2003 | 24 Sep 2003 | RELEASE_4_9_0 tag for ports/. | |
| Ports tree unfrozen | -- | -- | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 4.9-RELEASE. | |
| Final package build starts | 19 Sep 2003 | 10 Oct 2003 | The ports cluster and bento build final packages. | |
| doc/ tree tagged. | 20 Oct 2003 | 21 Oct 2003 | Version number bumps for doc/ subtree. RELEASE_4_9_0 tag for doc/. doc/ slush ends at this time. | |
| RELENG_4_9 branch | 18 Oct 2003 | 22 Oct 2003 | The release branch is created. | |
| Note to freebsd-stable@ | 18 Oct 2003 | 23 Oct 2003 | 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. | |
| Version numbers bumped. | 18 Oct 2003 | -- | -The files listed here + | The files listed here are updated to reflect the fact that this is FreeBSD 4.9. |
| Update man.cgi on the website. | 18 Oct 2003 | 19 Oct 2003 | Make sure the 4.9 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml. | |
| src tree tagged. | 21 Oct 2003 | -- | RELENG_4_9_0_RELEASE tag for src/. | |
| Final builds. | 21 Oct 2003 | -- | Final builds for x86 and Alpha in a pristine environment. | |
| Warn mirror-announce@FreeBSD.org | 21 Oct 2003 | -- | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master. | 21 Oct 2003 | -- | Release (and packages?) uploaded to ftp-master.FreeBSD.org | |
| Announcement | 23 Oct 2003 | -- | Announcement sent out after a majority of the mirrors have received the bits. | |
| Unfreeze the tree | 23 Oct 2003 | -- | 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_9 branch. |
This is a list of open issues that need to be resolved for FreeBSD 4.9. If you have any updates for this list, please e-mail re@FreeBSD.org.
As many of these open issues involve merging bus_dma driver changes - from -CURRENT, the busdma project page is + from -CURRENT, the busdma project page is also useful.
| Issue | Status | Responsible | Description |
|---|---|---|---|
| FireWire load failure bug. | Done | matusita@ | Reported on stable@. Did this ever work after the initial firewire commit to drivers.conf in April? If not, is there any reason to not just back out that commit and not have firewire supported during the install? |
| Issue | Status | Responsible | Description |
|---|---|---|---|
| if_dc tested/merged to work with PAE in 4.x | -- | luoqi | |
| busdma infrastructure merges | -- | scottl | It's unclear if further bus_dma infrastructure changes need to be merged? |
| if_xl | Done | silby | |
| RAID drivers tested/merged to work with PAE in 4.x | -- | scottl | |
| ACPI merged as optional component | In progress | John Baldwin | ACPI will be provided as an optional component, turned off by default. |
| Issue | Status | Responsible | Description |
|---|---|---|---|
| USB updated to work with PAE | In progress | jmg, joe, luoqi | USB does not currently work with PAE enabled. |
| twe updated for bus_dma/PAE | -- | ps | The 3ware twe driver needs to be updated for use with PAE in 4.X. |
| ciss updated for bus_dma/PAE | -- | ps | The ciss driver needs to be updated for use with PAE in 4.X. |
| Issue | Status | Responsible | Description |
|---|---|---|---|
| ACPI | Done | Murray | Handbook should be updated to note that ACPI can be enabled on 4.9 systems. |
| PAE | Done | Murray | Handbook should be updated to explain the basic PAE functionality. |
| Issue | Status | Responsible | Description |
|---|---|---|---|
| PAE testing | -- | More testing should be done with PAE systems to test device compatibility and performance. In particular, active systems with 12 gig of ram or more should be thoroughly tested to make sure the various memory allocation algorithms in the kernel still scale properly. There were reports of users running out of KVA space in -CURRENT with large memory machines. |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 5.0-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 5.0-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 5.0-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 5.0. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
One of the major new features of FreeBSD 5.0 will be completely re-worked SMP support.
-The current release engineering TODO list is also available. +
The current release engineering TODO list is also available. This list is updated periodically through the release cycle.
| Action | Expected | Actual | Description | |
| releng_5_dp1 branch (Perforce) | 15 Mar 2002 | 15 Mar 2002 | Branch created, commits require re@ approval. The branch will be used to allow us time to QA the release, synchronize the release notes with the translation teams, synchronize sysinstall and the package set, etc without disrupting the normal flow of development on -CURRENT. | |
| Ports Freeze | 2 Apr 2002 | 2 Apr 2002 | The ports tree is frozen and tagged for the developer preview. | |
| Final i386 package build completes | 3 Apr 2002 | 4 Apr 2002 | The final package build for the i386 architecture is complete. | |
| Final Alpha package build completes | 3 Apr 2002 | 5 Apr 2002 | The final package build for the Alpha architecture is complete. | |
| Final sparc64 package build completes | 3 Apr 2002 | 7 Apr 2002 | The final package build for the sparc64 architecture is complete. | |
| Package Split | 3 Apr 2002 | 7 Apr 2002 | The packages for the installation CDROM are selected from the results of the final package build. | |
| FreeBSD 5.0 Developer Preview 1 | 5 Apr 2002 | 8 Apr 2002 | A full release for the i386, Alpha, and sparc64 architectures. The i386 and Alpha releases at least will contain a full package set and a disc1 ISO image will be made available. | |
| 5.0 Feature List finalized | 16 Jun 2002 | -- | At the FreeBSD Developer Summit at Usenix, we will need to finalize the list of features that will be included with FreeBSD 5.0. Some features will just have to wait for 5.1 to give us ample time to QA the many features that are ready. | |
| RELENG_5_0_DP2 branch | 17 Jul 2002 | 17 Aug 2002 | Branch created in Perforce, commits require re@ approval. | |
| FreeBSD 5.0 Developer Preview 2 | 25 Jul 2002 | 18 Nov 2002 | A full release for the i386, Alpha, and sparc64 architectures. | |
| -CURRENT feature freeze | 1 Oct 2002 | 16 Oct 2002 | After this date, significant new features should be discussed with re@ before consideration for 5.0-RELEASE. | |
| -CURRENT code freeze | 20 Oct 2002 | 18 Nov 2002 | The code freeze for 5.0. Commits to HEAD require re@ approval. | |
| First release candidate | 2 Dec 2002 | 9 Dec 2002 | x86, alpha, sparc64, and ia64 images released and uploaded to ftp-master.FreeBSD.org. | |
| RELENG_5_0 branched | 12 Dec 2002 | 12 Dec 2002 | Branch from HEAD for the release. Note: no branch for RELENG_5 will happen a this time. | |
| src unfrozen | 12 Dec 2002 | 12 Dec 2002 | Unfreeze HEAD src. Continue to coordinate significant check-ins with re@FreeBSD.org in order to work towards 5-STABLE. | |
| Second release candidate | 17 Dec 2002 | 21 Dec 2002 | -- | |
| Ports tree tagged | 3 Jan 2003 | 1 Jan 2003 | Tentative date of RELEASE_5_0_0 tag for ports. | |
| Start RC3 builds | 7 Jan 2003 | 9 Jan 2003 | Set timestamp and start i386, pc98, sparc64, alpha, and ia64 builds. | |
| Third release candidate released | 10 Jan 2003 | 12 Jan 2003 | -- | |
| Version numbers bumped | 15 Jan 2003 | 15 Jan 2003 | -The files listed here + | The files listed here are updated to reflect FreeBSD 5.0. |
| src tree tagged | 15 Jan 2003 | 16 Jan 2003 | Tag the RELENG_5_0 branch with RELENG_5_0_0_RELEASE | |
| doc tree tagged | 15 Jan 2003 | 15 Jan 2003 | Tag the doc/ branch with RELEASE_5_0_0 | |
| Final builds | 15 Jan 2003 | 16 Jan 2003 | Start x86, alpha, sparc64, ia64, and pc98 builds. | |
| Warn hubs@FreeBSD.org | 15 Jan 2003 | 17 Jan 2003 | Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | 17 Jan 2003 | 17 Jan 2003 | Release and packages uploaded to ftp-master.FreeBSD.org | |
| FreeBSD 5.0 Released | 19 Jan 2003 | 19 Jan 2003 | FreeBSD 5.0 is announced to the mailing lists. | |
| FreeBSD 5.0 Press Release | 19 Jan 2003 | -- | A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications. |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 5.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 5.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 5.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 5.1. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
One of the major features of FreeBSD 5.1 will be further refinement of the re-worked SMP support introduced in FreeBSD 5.0.
FreeBSD 5.1 will continue to be released from the 5-CURRENT development stream. For more details about the milestones for reaching 5-STABLE, see the 5-STABLE Roadmap page.
-The current release engineering TODO list is also available. +
The current release engineering TODO list is also available. This list is updated periodically through the release cycle.
| Action | Expected | Actual | Description | |
| -CURRENT code freeze | 5 May 2003 | 5 May 2003 | The src/ code freeze for 5.1. Commits to HEAD require re@FreeBSD.org approval. | |
| 5.1-BETA | 5 May 2003 | 15 May 2003 | 5.1-BETA release of x86, alpha, sparc64, and ia64. | |
| 5.1-BETA2 | 19 May 2003 | 22 May 2003 | Second 5.1-BETA release of x86, alpha, sparc64, and ia64. | |
| RELENG_5_1 branched | 30 May 2003 | 31 May 2003 | Branch of src/ from HEAD for the release. Note: no branch for RELENG_5 will happen at this time. | |
| Turn off debugging for RELENG_5_1 | 30 May 2003 | 31 May 2003 | Turn off WITNESS, INVARIANTS, and malloc debugging options similar to what was done for 5.0. | |
| First release candidate | 30 May 2003 | 1 June 2003 | x86, alpha, sparc64, and ia64 images released and uploaded to ftp-master.FreeBSD.org. | |
| src/ unfrozen | 30 May 2003 | 31 May 2003 | Unfreeze HEAD src. Continue to coordinate significant check-ins with re@FreeBSD.org in order to work towards 5-STABLE. | |
| Ports tree tagged | 30 May 2003 | 27 May 2003 | Tentative date of RELEASE_5_1_0 tag for ports. | |
| Version numbers bumped | 2 June 2003 | 3 June 2003 | -The files listed here + | The files listed here are updated to reflect FreeBSD 5.1. |
| src/ tree tagged | 2 June 2003 | 4 June 2003 | Tag the RELENG_5_1 branch with RELENG_5_1_0_RELEASE. | |
| doc/ tree tagged | 2 June 2003 | 30 May 2003 | Tag the doc/ tree with RELEASE_5_1_0. | |
| Final builds | 2 June 2003 | 4 June 2003 | Start x86, alpha, sparc64, ia64, and pc98 builds. | |
| Warn hubs@FreeBSD.org | 5 June 2003 | 5 June 2003 | Heads up email to hubs@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | 5 June 2003 | 8 June 2003 | Release and packages uploaded to ftp-master.FreeBSD.org. | |
| FreeBSD 5.1 Released | 9 June 2003 | 9 June 2003 | FreeBSD 5.1 is announced to the mailing lists. | |
| FreeBSD 5.1 Press Release | 9 June 2003 | 9 June 2003 | A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications. |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 5.2.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 5.2.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 5.2.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 5.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 5.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 5.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 5.2. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
FreeBSD 5.2 will continue to be released from the 5-CURRENT development stream. For more details about the milestones for reaching 5-STABLE, see the 5-STABLE Roadmap page.
-The current release engineering TODO list is also available. +
The current release engineering TODO list is also available. This list is updated periodically through the release cycle.
| Action | Expected | Actual | Description | |
| src/ tree frozen | 17 Nov 2003 | 18 Nov 2003 | Announce the src/ code freeze for 5.2 on the HEAD branch. Commits to HEAD require re@FreeBSD.org approval. | |
| ports/ tree frozen | 17 Nov 2003 | 19 Nov 2003 | Announce the ports/ code freeze for 5.2. Commits to ports/ require portmgr@FreeBSD.org approval. | |
| Begin 5.2-BETA builds | 17 Nov 2003 | 24 Nov 2003 | Begin building 5.2-BETA disc1 and disc2 for all Tier-1 platforms. | |
| Release 5.2-BETA | 19 Nov 2003 | 26 Nov 2003 | 5.2-BETA tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| RELENG_5_2 branched | 1 Dec 2003 | 6 Dec 2003 | Branch of src/ from HEAD for the release. Note: no branch for RELENG_5 will happen at this time. | |
| Turn off debugging for RELENG_5_2 | 1 Dec 2003 | 6 Dec 2003 | Turn off WITNESS, INVARIANTS, and malloc debugging options similar to what was done for 5.1. | |
| Begin 5.2-RC1 builds | 1 Dec 2003 | 7 Dec 2003 | Begin building 5.2-RC1 disc1 and disc2 for all Tier-1 platforms. | |
| src/ unfrozen | 1 Dec 2003 | 6 Dec 2003 | Unfreeze HEAD src. Continue to coordinate significant check-ins with re@FreeBSD.org in order to work towards 5-STABLE. | |
| Release 5.2-RC1 | 3 Dec 2003 | 10 Dec 2003 | 5.2-RC1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree tagged | 3 Dec 2003 | 3 Dec 2003 | Tentative date of RELEASE_5_2_0 tag for ports. | |
| doc/ tree slush | 8 Dec 2003 | 9 Dec 2003 | Announce the doc/ slush for 5.2. From this time until the tagging of the doc/ tree, non-critical changes should be postponed to allow translation teams time to finish their work for the release. | |
| Begin 5.2-RC2 builds | 19 Dec 2003 | 21 Dec 2003 | Begin building 5.2-RC2 disc1 and disc2 for all Tier-1 platforms. | |
| Release 5.2-RC2 | 21 Dec 2003 | 23 Dec 2003 | 5.2-RC2 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| doc/ tree tagged | 12 Dec 2003 | 12 Dec 2003 | Tag the doc/ tree with RELEASE_5_2_0. | |
| Version numbers bumped | Jan 2004 | Jan 11 2004 | -The files listed here + | The files listed here are updated to reflect FreeBSD 5.2. |
| src/ tree tagged | Jan 2004 | Jan 11 2004 | Tag the RELENG_5_2 branch with RELENG_5_2_0_RELEASE. | |
| Begin 5.2-RELEASE builds | Jan 2004 | Jan 11 2004 | Start 5.2-RELEASE Tier-1 builds. | |
| Warn mirror-announce@FreeBSD.org | Jan 2004 | Jan 11 2004 | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | Jan 2004 | Jan 11 2004 | Release and packages uploaded to ftp-master.FreeBSD.org. | |
| FreeBSD 5.2 Announced | Jan 2004 | Jan 12 2004 | FreeBSD 5.2 is announced to the mailing lists. | |
| FreeBSD 5.2 Press Release | Jan 2004 | Jan 12 2004 | A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications. |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 5.3-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 5.3-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 5.3-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 5.3. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
FreeBSD 5.3 will be the first release from the RELENG_5 branch and thus will also be the first 5-STABLE release.
-The current release engineering TODO list is also available. +
The current release engineering TODO list is also available. This list is updated periodically through the release cycle.
| Action | Expected | Actual | Description | |
| Announce the Ports Freeze | 15 Aug 2004 | 15 Aug 2004 | Someone from portmgr@ should email for the two week long ports freeze and tagging of the ports tree. | |
| src/ tree frozen | 16 Aug 2004 | 16 Aug 2004 | Announce the src/ code freeze for 5.3. Commits to the HEAD branch will be locked until the RELENG_5 branch is created. | |
| RELENG_5 branch creation | 16 Aug 2004 | 17 Aug 2004 | Create the RELENG_5 branch. Commits to this branch will require Release Engineering approval until the RELENG_5_3 branch is created. | |
| Begin 5.3-BETA1 builds | 16 Aug 2004 | 20 Aug 2004 | Begin building 5.3-BETA1 disc1 and disc2 for all Tier-1 platforms. The first built typically requires several days to resolve latent problems on all platforms, so it will be started early. | |
| Release 5.3-BETA1 | 20 Aug 2004 | 22 Aug 2004 | 5.3-BETA1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| Build and release 5.3-BETA2 | 27 Aug 2004 | 29 Aug 2004 | 5.3-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Build and release 5.3-BETA3 | 3 Sep 2004 | 5 Sep 2004 | 5.3-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree frozen | 3 Sep 2004 | 3 Sep 2004 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Build and release 5.3-BETA4 | 10 Sep 2004 | 12 Sep 2004 | 5.3-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Build and release 5.3-BETA5 | 17 Sep 2004 | 20 Sep 2004 | 5.3-BETA5 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree tagged | 17 Sep 2004 | 11 Oct 2004 | RELEASE_5_3_0 tag for ports/. | |
| Ports tree unfrozen | 17 Sep 2004 | 11 Oct 2004 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 5.3-RELEASE. | |
| Final package build starts | 17 Sep 2004 | 11 Oct 2004 | The ports cluster and pointyhat build final packages. | |
| Turn off debugging for RELENG_5 | 17 Sep 2004 | 7 Sep 2004 | Turn off WITNESS, INVARIANTS, and malloc debugging options. This will be the default for all RELENG_5 releases. | |
| doc/ tree slush | 17 Sep 2004 | 17 Sep 2004 | Announce the doc/ slush for 5.3. From this time until the tagging of the doc/ tree, non-critical changes should be postponed to allow translation teams time to finish their work for the release. If we can resolve problems before this expected date, doc/ slush could start earlier. At this point, we are considering on 10 Sep at earliest, and on 17 Sep at latest. | |
| Build and release 5.3-BETA6 | 24 Sep 2004 | 26 Sep 2004 | 5.3-BETA6 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| doc/ tree tagged | 24 Sep 2004 | 26 Sep 2004 | Tag the doc/ tree with RELEASE_5_3_0. | |
| Build and release 5.3-BETA7 | 1 Oct 2004 | 3 Oct 2004 | 5.3-BETA7 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| RELENG_5_3 branched | 8 Oct 2004 | 16 Oct 2004 | Branch of src/ from RELENG_5 for the release. | |
| src/ unfrozen | 8 Oct 2004 | 16 Oct 2004 | Unfreeze RELENG_5 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final. | |
| Build and release 5.3-RC1 | 17 Oct 2004 | 19 Oct 2004 | 5.3-RC1 tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| Version numbers bumped | 22 Oct 2004 | 24 Oct 2004 | -The files listed here + | The files listed here are updated to reflect FreeBSD 5.3. |
| src/ tree tagged | 22 Oct 2004 | 24 Oct 2004 | Tag the RELENG_5_3 branch with RELENG_5_3_0_RELEASE. | |
| Begin 5.3-RELEASE builds | 5 Nov 2004 | 4 Nov 2004 | Start 5.3-RELEASE Tier-1 builds. | |
| Warn mirror-announce@FreeBSD.org | 5 Nov 2004 | 5 Nov 2004 | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | 5 Nov 2004 | 6 Nov 2004 | Release and packages uploaded to ftp-master.FreeBSD.org. | |
| FreeBSD 5.3 Announced | 5 Nov 2004 | 6 Nov 2004 | FreeBSD 5.3 is announced to the mailing lists. | |
| FreeBSD 5.3 Press Release | 5 Nov 2004 | 6 Nov 2004 | A formal press release statement is in the works and should be released at this time to the www.FreeBSD.org website and various tech publications. |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 5.4-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 5.4-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 5.4-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
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 + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
| Reminder announcement | 31 Jan 2005 | 31 Jan 2005 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 5.4 release. | |
| Announce the Ports Freeze | 24 Feb 2005 | 24 Feb 2005 | Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| 5.4-PRERELEASE | 23 Feb 2005 | 24 Feb 2005 | newvers.sh updated. | |
| Code freeze begins | 2 Mar 2005 | 3 Mar 2005 | After this date, all commits to the RELENG_5 branch 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. | |
5.4-BETA1 |
4 Mar 2005 | 20 Mar 2005 | First public test release build. Note that the release build name is 5.4-BETA1 but newvers.sh RELEASE name remains 5.4-PRERELEASE. This is because the name BETA often confuses the users who are using the STABLE branch. | |
| Announce doc/ tree slush | 14 Mar 2005 | 25 Mar 2005 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| Ports tree frozen | 21 Mar 2005 | 21 Mar 2005 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| doc/ tree slush | 2 Apr 2005 |
2 Apr 2005 |
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. | 11 Apr 2005 |
12 Apr 2005 | Version number bumps for doc/ subtree. RELEASE_5_4_0 tag for doc/. doc/ slush ends at this time. | |
| RELENG_5_4 branch | 31 Mar 2005 | 3 Apr 2005 | The release branch is created. Update newvers.sh and release.ent on various branches involved. | |
| Unfreeze the tree | 31 Mar 2005 | 3 Apr 2005 | Announcement to developers explaining that commits to RELENG_5 no longer require approval. Also note the policy for commits to the RELENG_5_4 branch. | |
| 5.4-RC1 | 31 Mar 2005 | 3 Apr 2005 | newvers.sh and release.ent updated. | |
| Ports tree tagged | 31 Mar 2005 | 2 Apr 2005 | RELEASE_5_4_0 tag for ports/. | |
| Ports tree unfrozen | 31 Mar 2005 | 2 Apr 2005 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 5.4-RELEASE. | |
| Final package build starts | 31 Mar 2005 | -- | The ports cluster and pointyhat build final packages. | |
| First release candidate | 2 Apr 2005 | 5 Apr 2005 | 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 packages/ directory should be a relative symlink, as described in the releng article. When the builds begin send a note to mirror-announce@FreeBSD.org saying a "Normal Release Cycle" is beginning, RC ISOs and install directories will be coming through the next few weeks. | |
| Heads up to -stable | 2 Apr 2005 | 5 Apr 2005 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the first snapshot is uploaded. | |
| Second release candidate | 9 Apr 2005 | 9 Apr 2005 | Note: the release date of this candidate depends on the user experience with RC1. | |
| Heads up to -stable | 9 Apr 2005 | 11 Apr 2005 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the second snapshot is uploaded. | |
| Third release candidate | 16 Apr 2005 | 16 Apr 2005 | Note: the release date of this candidate depends on the user experience with RC2. | |
| Heads up to -stable | 16 Apr 2005 | 18 Apr 2005 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the third snapshot is uploaded. | |
| Fourth release candidate | 30 Apr 2005 | 2 May 2005 | Note: This is the final release candidate. | |
| Heads up to -stable | 1 May 2005 | 2 May 2005 | A message should be sent to qa@FreeBSD.org and stable@FreeBSD.org after the fourth snapshot is uploaded. | |
| Version numbers bumped. | 6 May 2005 | 6 May 2005 | -The files listed + | The files listed here are updated to reflect the fact that this is FreeBSD 5.4. |
| src tree tagged. | 6 May 2005 | 6 May 2005 | RELENG_5_4_0_RELEASE tag for src/. | |
| Final builds. | 6 May 2005 | 6 May 2005 | Final builds for all architectures in a pristine environment. | |
| Warn mirror-announce@FreeBSD.org | 6 May 2005 | 6 May 2005 | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master. | 7 May 2005 | -- | Release uploaded to ftp-master.FreeBSD.org (packages should have been done before now, otherwise it chokes the mirror sites and propagation of the release bits takes too long) | |
| Update man.cgi on the website. | 9 May 2005 | -- | Make sure the 5.4 manual pages are being displayed by default for the man->web gateway. Also make sure these man pages are pointed to by docs.xml. | |
| Announcement | 9 May 2005 | -- | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to the secteam | 17 May 2005 | -- | RELENG_5_4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.
General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. - MFC + MFC requests should be sent to re@FreeBSD.org.
| Committer | Area | Expiration |
|---|
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 5.5-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 5.5-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 5.5-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 5.5. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
|---|---|---|---|---|
| Reminder announcement | -- | 25 January 2006 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 5.5 release. | |
| Code freeze begins | 31 January 2006 | 31 January 2006 | 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 the Ports Freeze | -- | 5 February 2006 | Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| Begin 5.5-BETA1 builds | 5 February 2006 | 5 February 2006 | Begin building the first public test release build for all Tier-1 platforms. | |
| Release 5.5-BETA1 | 5 February 2006 | 5 February 2006 | 5.5-BETA1 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 5.5-BETA2 builds | 19 February 2006 | 16 February 2006 | Begin building the second public test release build for all Tier-1 platforms. | |
| Release 5.5-BETA2 | 19 February 2006 | 20 February 2006 | 5.5-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree frozen | 20 February 2006 | 23 February 2006 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Begin 5.5-BETA3 builds | 5 March 2006 | 1 March 2006 | Begin building the third public test release build for all Tier-1 platforms. | |
| Release 5.5-BETA3 | 5 March 2006 | 5 March 2006 | 5.5-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Announce doc/ tree slush | 6 March 2006 | 6 March 2006 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| Begin 5.5-BETA4 builds | -- | 14 March 2006 | Begin building the fourth public test release build for all Tier-1 platforms. | |
| Release 5.5-BETA4 | -- | 14 March 2006 | 5.5-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree tagged | 6 March 2006 | 14 March 2006 | RELEASE_5_5_0 tag for ports/. | |
| Ports tree unfrozen | 6 March 2006 | 14 March 2006 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 5.5-RELEASE. | |
| Final package build starts | TBD | -- | The ports cluster and pointyhat build final packages. | |
| doc/ tree slush | 10 March 2006 | 7 April 2006 | 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. | 13 March 2006 | 21 May 2006 | Version number bumps for doc/ subtree. RELEASE_5_5_0 tag for doc/. doc/ slush ends at this time. | |
| RELENG_5_5 branch | 12 May 2006 |
12 May 2006 | The new major version branch is created. Update newvers.sh and release.ent on various branches involved. | |
| src/ unfrozen | TBD | -- | Unfreeze RELENG_5 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final. | |
| Build 5.5-RC1 | 14 May 2006 |
13 May 2006 | Begin building the first release candidate build for all Tier-1 platforms. | |
| Release 5.5-RC1 | 14 May 2006 |
16 May 2006 | 5.5-RC1 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org. | |
| Version numbers bumped | 20 May 2006 |
12 May 2006 | -The files listed here + | The files listed here are updated to reflect FreeBSD 5.5. |
| src/ tree tagged | 20 May 2006 |
22 May 2006 | Tag the RELENG_5_5 branch with RELENG_5_5_0_RELEASE. | |
| Begin 5.5-RELEASE builds | 20 May 2006 |
22 May 2006 | Start 5.5-RELEASE Tier-1 builds. | |
| Warn mirror-announce@FreeBSD.org | 20 May 2006 |
23 May 2006 | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | 21 May 2006 |
24 May 2006 | Release and packages uploaded to ftp-master.FreeBSD.org. | |
| Announcement | 22 May 2006 |
25 May 2006 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to the secteam | TBD | 31 May 2006 | RELENG_5_5 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.
General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. - MFC + MFC requests should be sent to re@FreeBSD.org.
| Committer | Area | Expiration |
|---|---|---|
| Ruslan Ermilov | manual pages | 1 July 2005 |
| Joseph Koshy | Performance measurement toolset work: sys/dev/hwpmc, usr.sbin/pmcstat, etc. | 1 July 2005 |
| Max Laier | IP6FW removal, contrib/pf PR bugfixes, if_bridge cleanup. | 1 July 2005 |
| Jeff Roberson | VFS stability fixes. | 1 July 2005 |
| Brooks Davis | ifnet restructuring fixes. | 1 July 2005 |
| Christian Brueffer | manual pages and release documentation | 1 July 2005 |
| Bruce A. Mah | release documentation | 1 July 2005 |
| Wilko Bulte | Alpha release documentation | 1 July 2005 |
| Peter Wemm | i386 / amd64 syncing | 1 July 2005 |
| Robert Watson | minor manual page tweaks | 1 July 2005 |
| Denis Peplin | ru_RU.KOI8-R translation of release documentation | 1 July 2005 |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 6.0-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 6.0-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 6.0-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 6.0. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
|---|---|---|---|---|
| Reminder announcement | 3 June 2005 | 3 June 2005 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.0 release. | |
| Announce the Ports Freeze | 22 July 2005 | 22 July 2005 | 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 | 10 June 2005 | 10 June 2005 | 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 | -- | 2 October 2005 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| Ports tree frozen | 1 August 2005 | 1 August 2005 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| doc/ tree slush | 5 October 2005 | 5 October 2005 | 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. | 10 October 2005 | 12 October 2005 | Version number bumps for doc/ subtree. RELEASE_6_0_0 tag for doc/. doc/ slush ends at this time. | |
| RELENG_6 branch | 10 July 2005 | 11 July 2005 | The new major version branch is created. Update newvers.sh and release.ent on various branches involved. | |
| Begin 6.0-BETA1 builds | -- | 11 July 2005 | Begin building the first public test release build for all Tier-1 platforms. | |
| Release 6.0-BETA1 | -- | 15 July 2005 | 6.0-BETA1 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 6.0-BETA2 builds | -- | 1 August 2005 | Begin building the second public test release build for all Tier-1 platforms. | |
| Release 6.0-BETA2 | -- | 5 August 2005 | 6.0-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 6.0-BETA3 builds | 20 August 2005 | 25 August 2005 | Begin building the third public test release build for all Tier-1 platforms. | |
| Release 6.0-BETA3 | 22 August 2005 | 29 August 2005 | 6.0-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 6.0-BETA4 builds | -- | 3 September 2005 | Begin building the fourth public test release build for all Tier-1 platforms. | |
| Release 6.0-BETA4 | -- | 7 September 2005 | 6.0-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 6.0-BETA5 builds | -- | 17 September 2005 | Begin building the fifth public test release build for all Tier-1 platforms. | |
| Release 6.0-BETA5 | -- | 30 September 2005 | 6.0-BETA5 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| RELENG_6_0 branch | TBD |
9 October 2005 | The new release branch is created. Update newvers.sh and release.ent on various branches involved. | |
| src/ unfrozen | TBD | -- | Unfreeze RELENG_6 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final. | |
| Ports tree tagged | 28 August 2005 |
28 August 2005 | RELEASE_6_0_0 tag for ports/. | |
| Ports tree unfrozen | 28 August 2005 |
28 August 2005 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.0-RELEASE. | |
| Final package build starts | 28 August 2005 |
28 August 2005 | The ports cluster and pointyhat build final packages. | |
| Build 6.0-RC1 | 5 October 2005 | 9 October 2005 | Begin building the first release candidate build for all Tier-1 platforms. | |
| Release 6.0-RC1 | TBD | 11 October 2005 | 6.0-RC1 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org. | |
| Version numbers bumped | TBD | -- | -The files listed here + | The files listed here are updated to reflect FreeBSD 6.0. |
| src/ tree tagged | TBD | -- | Tag the RELENG_6_0 branch with RELENG_6_0_0_RELEASE. | |
| Begin 6.0-RELEASE builds | TBD | -- | Start 6.0-RELEASE Tier-1 builds. | |
| Warn mirror-announce@FreeBSD.org | TBD | -- | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | TBD | -- | Release and packages uploaded to ftp-master.FreeBSD.org. | |
| Announcement | TBD |
-- | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to the secteam | TBD | -- | RELENG_6_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.
General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. - MFC + MFC requests should be sent to re@FreeBSD.org.
| Committer | Area | Expiration |
|---|
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 6.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 6.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 6.1-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 6.1. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
|---|---|---|---|---|
| Reminder announcement | -- | 25 January 2006 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.1 release. | |
| Code freeze begins | 31 January 2006 | 31 January 2006 | 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 the Ports Freeze | -- | 5 February 2006 | Someone from portmgr@ should email freebsd-ports@ to set a date for the week long ports freeze and tagging of the ports tree. | |
| Begin 6.1-BETA1 builds | 5 February 2006 | 5 February 2006 | Begin building the first public test release build for all Tier-1 platforms. | |
| Release 6.1-BETA1 | 5 February 2006 | 5 February 2006 | 6.1-BETA1 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 6.1-BETA2 builds | 19 February 2006 | 16 February 2006 | Begin building the second public test release build for all Tier-1 platforms. | |
| Release 6.1-BETA2 | 19 February 2006 | 20 February 2006 | 6.1-BETA2 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree frozen | 20 February 2006 | 23 February 2006 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Begin 6.1-BETA3 builds | -- | 1 March 2006 | Begin building the third public test release build for all Tier-1 platforms. | |
| Release 6.1-BETA3 | -- | 3 March 2006 | 6.1-BETA3 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 6.1-BETA4 builds | 12 March 2006 | 13 March 2006 | Begin building the fourth public test release build for all Tier-1 platforms. | |
| Release 6.1-BETA4 | -- | 14 March 2006 | 6.1-BETA4 tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| RELENG_6_1 branch | 5 April 2006 |
5 April 2006 | The new major version branch is created. Update newvers.sh and release.ent on various branches involved. | |
| src/ unfrozen | TBD | -- | Unfreeze RELENG_6 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final. | |
| Build 6.1-RC1 | 5 April 2006 |
5 April 2006 | Begin building the first release candidate build for all Tier-1 platforms. | |
| Release 6.1-RC1 | 10 April 2006 |
-- | 6.1-RC1 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree tagged | 6 March 2006 | 14 March 2006 | RELEASE_6_1_0 tag for ports/. | |
| Ports tree unfrozen | 6 March 2006 | 14 March 2006 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.1-RELEASE. | |
| Final package build starts | TBD | -- | The ports cluster and pointyhat build final packages. | |
| Announce doc/ tree slush | 6 March 2006 | 6 March 2006 | Notification of the impending doc/ tree slush should be sent to doc@. | |
| doc/ tree slush | 7 April 2006 |
7 April 2006 | 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. | |
| Build 6.1-RC2 | 30 April 2006 |
30 April 2006 | Begin building the second release candidate build for all Tier-1 platforms. | |
| Release 6.1-RC2 | 2 May 2006 |
2 May 2006 | 6.1-RC2 tier-1 platform images released, and uploaded to ftp-master.FreeBSD.org. | |
| doc/ tree tagged. | 10 April 2006 |
17 April 2006 | Version number bumps for doc/ subtree. RELEASE_6_1_0 tag for doc/. doc/ slush ends at this time. | |
| Version numbers bumped | 7 May 2006 |
-- | -The files listed here + | The files listed here are updated to reflect FreeBSD 6.1. |
| src/ tree tagged | 7 May 2006 |
7 May 2006 | Tag the RELENG_6_1 branch with RELENG_6_1_0_RELEASE. | |
| Begin 6.1-RELEASE builds | 7 May 2006 |
7 May 2006 | Start 6.1-RELEASE Tier-1 builds. | |
| Warn mirror-announce@FreeBSD.org | 7 May 2006 |
-- | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | 8 May 2006 |
8 May 2006 | Release and packages uploaded to ftp-master.FreeBSD.org. | |
| Announcement | 8 May 2006 |
8 May 2006 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to the secteam | TBD | -- | RELENG_6_1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.
General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. - MFC + MFC requests should be sent to re@FreeBSD.org.
| Committer | Area | Expiration |
|---|---|---|
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 6.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 6.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 6.2-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 6.2. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description | |
|---|---|---|---|---|
| Reminder announcement | 8 September 2006 | 8 September 2006 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.2 release. | |
| Code freeze begins | 10 September 2006 | 10 September 2006 | After this date, all commits to RELENG_6 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 the Ports Freeze | 17 September 2006 | 17 September 2006 | portmgr@ sends email to freebsd-ports@ to announce the dates for the week long ports freeze and tagging of the ports tree. | |
| Begin 6.2-BETA1 builds | 16 September 2006 | 16 September 2006 | Begin building the first public test release build for all Tier-1 platforms. | |
| Release 6.2-BETA1 | 17 September 2006 | 20 September 2006 | 6.2-BETA1 Tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Begin 6.2-BETA2 builds | 30 September 2006 | 1 October 2006 | Begin building the second public test release build for all Tier-1 platforms. | |
| Release 6.2-BETA2 | 1 October 2006 | 5 October 2006 | 6.2-BETA2 Tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree frozen | 10 October 2006 | 10 October 2006 | Only approved commits will be permitted to the ports/ tree during the freeze. | |
| Begin 6.2-BETA3 builds | 30 October 2006 | 30 October 2006 | Begin building the third public test release build for all Tier-1 platforms. | |
| Release 6.2-BETA3 | 1 November 2006 | 31 October 2006 | 6.2-BETA3 Tier-1 platform images built, released, and uploaded to ftp-master.FreeBSD.org. | |
| RELENG_6_2 branch | 12 October 2006 | 15 November 2006 | The release branch is created. Update newvers.sh and release.ent on various branches involved. | |
| src/ unfrozen | 14 October 2006 | 18 November 2006 | Unfreeze RELENG_6 src. Continue to coordinate significant check-ins with re@FreeBSD.org until the release is final. | |
| Build 6.2-RC1 | 14 October 2006 | 15 November 2006 | Begin building the first release candidate build for all Tier-1 platforms. | |
| Release 6.2-RC1 | 15 October 2006 | 17 November 2006 | 6.2-RC1 Tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| Ports tree tagged | 24 October 2006 | 30 October 2006 | RELEASE_6_2_0 tag for ports/. | |
| Ports tree slush | 24 October 2006 | 30 October 2006 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.2-RELEASE. Also, wide sweeping commits are only allowed after explicit approval from portmgr@. The ports tree will be fully unfrozen after the release announcement. | |
| Final package build starts | 24 October 2006 | 20 November 2006 | The ports cluster and pointyhat build final packages. | |
| Announce doc/ tree slush | 8 October 2006 | -- | Notification of the impending doc/ tree slush should be sent to doc@. | |
| doc/ tree slush | 23 October 2006 | -- | 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. | |
| Build 6.2-RC2 | 25 November 2006 |
24 December 2006 | Begin building the second release candidate build for all Tier-1 platforms. | |
| Release 6.2-RC2 | 27 November 2006 |
27 December 2006 | 6.2-RC2 Tier-1 platform images released and uploaded to ftp-master.FreeBSD.org. | |
| doc/ tree tagged. | 29 October 2006 | 8 December 2006 | Version number bumps for doc/ subtree. RELEASE_6_2_0 tag for doc/. doc/ slush ends at this time. | |
| Version numbers bumped | 8 January 2007 |
11 January 2007 | -The files listed here + | The files listed here are updated to reflect FreeBSD 6.2. |
| src/ tree tagged | 8 January 2007 |
11 January 2007 | Tag the RELENG_6_2 branch with RELENG_6_2_0_RELEASE. | |
| Begin 6.2-RELEASE builds | 8 January 2007 |
11 January 2007 | Start 6.2-RELEASE Tier-1 builds. | |
| Warn mirror-announce@FreeBSD.org | 8 January 2007 |
-- | Heads up email to mirror-announce@FreeBSD.org to give admins time to prepare for the load spike to come. The site administrators have frequently requested advance notice for new ISOs. | |
| Upload to ftp-master | 8 January 2007 |
13 January 2007 | Release and packages uploaded to ftp-master.FreeBSD.org. | |
| Announcement | 10 January 2007 |
15 January 2007 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to so@ | TBD | 22 January 2007 | Control of the RELENG_6_2 branch is handed over to the FreeBSD Security Officer Team one or two weeks after the announcement. |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 6.3-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 6.3-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 6.3-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 6.3. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description |
| Reminder announcement | TBD | 15 Oct 2007 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.3 release. |
| Announce the Ports Freeze | 23 Oct 2007 | 23 Oct 2007 | 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 Nov 2007 | 18 Nov 2007 | After this date, all commits to RELENG_6 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 | 19 Nov 2007 | Notification of the impending doc/ tree slush should be sent to doc@. |
| Ports tree frozen | 30 Oct 2007 | 30 Oct 2007 | Only approved commits will be permitted to the ports/ tree during the freeze. |
| doc/ tree slush | 25 Nov 2007 | 25 Nov 2007 | 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. | 5 Dec 2007 | 5 Dec 2007 | Version number bumps for doc/ subtree. RELEASE_6_3_0 tag for doc/. doc/ slush ends at this time. |
| BETA1 builds | 24 Oct 2007 | 1 Nov 2007 | Begin BETA1 builds. |
| BETA2 builds | 7 Nov 2007 | 9 Nov 2007 | Begin BETA2 builds. |
| RELENG_6_3 branch | 21 Nov 2007 | 25 Nov 2007 | The new release branch is created. Update newvers.sh and release.ent on various branches involved. |
| RC1 builds | 21 Nov 2007 | 26 Nov 2007 | Begin RC1 builds. |
| RC2 builds | 5 Dec 2007 | 22 Dec 2007 | Begin RC2 builds. |
| Ports tree tagged | 14 Dec 2007 | 11 Dec 2007 | RELEASE_6_3_0 tag for ports/. |
| Ports tree unfrozen | 14 Dec 2007 | 11 Dec 2007 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.3-RELEASE. |
| Final package build starts | 14 Dec 2007 | 12 Dec 2007 | The ports cluster and pointyhat build final packages. |
| RELEASE builds | 19 Dec 2007 | 15 Jan 2008 | Begin RELEASE builds. |
| Announcement | 23 Dec 2007 | 18 Jan 2008 | Announcement sent out after a majority of the mirrors have received the bits. |
| Turn over to the secteam | TBD | 28 Jan 2008 | RELENG_6_3 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The hardware notes for FreeBSD are customized for different platforms, as many devices are only supported on (or are only relevant for) specific processors or architectures.
Hardware notes for FreeBSD 6.4-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The installation notes for FreeBSD are customized for different platforms, as the procedures for installing FreeBSD are highly dependent on the hardware platform.
Installation notes for FreeBSD 6.4-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
The highlights in the 6.4-RELEASE are the following:
New and much-improved NFS Lock Manager (NLM) client
Support for the Camellia cipher
Boot loader changes allow, among other things, booting from USB devices and booting from GPT-labeled devices with GPT-enabled BIOSes
DVD install ISO images for amd64/i386
KDE updated to 3.5.10, GNOME updated to 2.22.3
Updates for BIND, sendmail, OpenPAM, and others
For more details, please see the Release Notes below.
The release notes for FreeBSD are customized for different platforms, as some of the changes made to FreeBSD apply only to specific processor architectures.
Release notes for FreeBSD 6.4-RELEASE are available for the following platforms:
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is a specific schedule for the release of FreeBSD 6.4. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description |
| Reminder announcement | -- | 22 August 2008 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 6.4 release. |
| Announce the Ports Freeze | -- | 22 August 2008 | 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 | 29 August 2008 | 2 September 2008 | 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 | 8 September 2008 | 8 September 2008 | Only approved commits will be permitted to the ports/ tree during the freeze. |
| doc/ tree slush | 8 September 2008 | 8 September 2008 | 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. | 15 September 2008 | 16 September 2008 | Version number bumps for doc/ subtree. RELEASE_6_4_0 tag for doc/. doc/ slush ends at this time. |
| BETA1 builds | 1 September 2008 | 5 September 2008 | Begin BETA1 builds. |
| RELENG_6_4 branch | 6 September 2008 | 2 October 2008 | The new release branch is created. Update newvers.sh and release.ent on various branches involved. |
| RC1 builds | 8 September 2008 | 5 October 2008 | Begin RC1 builds. |
| Ports tree tagged | 15 September 2008 | 22 September 2008 | RELEASE_6_4_0 tag for ports/. |
| Ports tree unfrozen | 15 September 2008 | 22 September 2008 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 6.4-RELEASE. |
| Final package build starts | 15 September 2008 | 22 September 2008 | The ports cluster and pointyhat build final packages. |
| RC2 builds | 22 September 2008 | 2 November 2008 | Begin RC2 builds. |
| RELEASE builds | 12 November 2008 | 26 November 2008 | Begin RELEASE builds. |
| Announcement | 28 November 2008 | Announcement sent out after a majority of the mirrors have received the bits. | |
| Turn over to the secteam | TBD | 12 December 2008 | RELENG_6_4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The release engineering team utilizes a code freeze to maintain stability in the period immediately preceding a release. The developers below have been given explicit approval by re@ to continue conservative work in a narrowly defined area until the expiration dates below. All other developers are required to get approval for each individual change from re@ before committing to the release branch.
General discussions about the release engineering process or quality assurance issues should be sent to the public freebsd-qa mailing list. - MFC + MFC requests should be sent to re@FreeBSD.org.
| Committer | Area | Expiration |
|---|---|---|
| No approval granted yet. | ||
This is a specific schedule for the release of FreeBSD 7.0. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description |
| Reminder announcement | TBD | 15 Oct 2007 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 7.0 release. |
| Announce the Ports Freeze | 23 Oct 2007 | 23 Oct 2007 | 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 | 19 Nov 2007 | Notification of the impending doc/ tree slush should be sent to doc@. |
| Ports tree frozen | 30 Oct 2007 | 30 Oct 2007 | Only approved commits will be permitted to the ports/ tree during the freeze. |
| doc/ tree slush | 25 Nov 2007 | 25 Nov 2007 | 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. | 5 Dec 2007 | 5 Dec 2007 | Version number bumps for doc/ subtree. RELEASE_7_0_0 tag for doc/. doc/ slush ends at this time. |
| RELENG_7 branch | -- | 11 Oct 2007 | The new major version branch is created. Update newvers.sh and release.ent on various branches involved. |
| BETA1 builds | 17 Oct 2007 | 19 Oct 2007 | Begin BETA1 builds. |
| BETA2 builds | 31 Oct 2007 | 31 Oct 2007 | Begin BETA2 builds. |
| BETA3 builds | 14 Nov 2007 | 16 Nov 2007 | Begin BETA3 builds. |
| BETA4 builds | 28 Nov 2007 | 2 Dec 2007 | Begin BETA4 builds. |
| RELENG_7_0 branch | 12 Dec 2007 | 22 Dec 2007 | The new release branch is created. Update newvers.sh and release.ent on various branches involved. |
| RC1 builds | 12 Dec 2007 | 22 Dec 2007 | Begin RC1 builds. |
| RC2 builds | 28 Jan 2008 | 7 Feb 2008 | Begin RC2 builds. |
| Ports tree tagged | 14 Dec 2007 | 11 Dec 2007 | RELEASE_7_0_0 tag for ports/. |
| Ports tree unfrozen | 14 Dec 2007 | 11 Dec 2007 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 7.0-RELEASE. |
| Final package build starts | 14 Dec 2007 | 12 Dec 2007 | The ports cluster and pointyhat build final packages. |
| RELEASE builds | 11 Feb 2008 | 23 Feb 2008 | Begin RELEASE builds. |
| Announcement | 26 Feb 2008 | 27 Feb 2008 | Announcement sent out after a majority of the mirrors have received the bits. |
| Turn over to the secteam | TBD | 5 Mar 2008 | RELENG_7_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
This is a specific schedule for the release of FreeBSD 7.1. For more general information about the release engineering process, - please see the Release + 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 + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description |
| Reminder announcement | -- | 22 August 2008 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 7.1 release. |
| Announce the Ports Freeze | -- | 22 August 2008 | 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 | 29 August 2008 | 2 September 2008 | After this date, all commits to RELENG_7 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 | -- | 2 September 2008 | Notification of the impending doc/ tree slush should be sent to doc@. |
| Ports tree frozen | 8 September 2008 | 8 September 2008 | Only approved commits will be permitted to the ports/ tree during the freeze. |
| doc/ tree slush | 8 September 2008 | 8 September 2008 | 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. | 15 September 2008 | 16 September 2008 | Version number bumps for doc/ subtree. RELEASE_7_1_0 tag for doc/. doc/ slush ends at this time. |
| BETA1 builds | 1 September 2008 | 5 September 2008 | Begin BETA1 builds. |
| BETA2 builds | -- | 19 October 2008 | Begin BETA2 builds. |
| RELENG_7_1 branch | 6 September 2008 | 25 November 2008 | The new release branch is created. Update newvers.sh and release.ent on various branches involved. |
| RC1 builds | 15 September 2008 | 8 December 2008 | Begin RC1 builds. |
| Ports tree tagged | 15 September 2008 | 22 September 2008 | RELEASE_7_1_0 tag for ports/. |
| Ports tree unfrozen | 15 September 2008 | 22 September 2008 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 7.1-RELEASE. |
| Final package build starts | 15 September 2008 | 22 September 2008 | The ports cluster and pointyhat build final packages. |
| RC2 builds | 29 September 2008 | 22 December 2008 | Begin RC2 builds. |
| RELEASE builds | TBD | 1 January 2009 | Begin RELEASE builds. |
| Announcement | 13 October 2008 | 5 January 2009 | Announcement sent out after a majority of the mirrors have received the bits. |
| Turn over to the secteam | TBD | -- | RELENG_7_1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The highlights in the 7.2-RELEASE are the following:
[amd64, i386] The FreeBSD virtual memory subsystem now
supports fully transparent use of superpages for application memory;
application memory pages are dynamically promoted to or
demoted from superpages without any modification to
application code. This change offers the benefit of large page
sizes such as improved virtual memory efficiency and reduced
TLB (translation lookaside buffer) misses without downsides
like application changes and virtual memory
inflexibility. This is disabled by default and can be enabled
by setting a loader tunable vm.pmap.pg_ps_enabled to 1.
[amd64] The FreeBSD kernel virtual address space has been increased to 6GB. This allows subsystems to use larger virtual memory space than before. For example, zfs(8) adaptive replacement cache (ARC) requires large kernel memory space to cache file system data, so it benefits from the increased address space. Note that the ceiling on the kernel map size is now 60% of the size rather than an absolute quantity.
[sparc64] The FreeBSD now supports Ultra SPARC III (Cheetah) processor family.
[i386] The boot(8) BTX loader has been improved. This fixes several boot issues on recent machines reported for 7.1-RELEASE and before.
A bug in the ciss(4) driver which caused low “max device openings” count and led to poor performance has been fixed.
The sdhci(4) driver has been added. This supports PCI devices with class 8 and subclass 5 according to the SD Host Controller Specification.
Various network interface drivers have been improved, including ae(4), ath_hal(4), axe(4), bce(4), cxgb(4), fxp(4), igb(4), jme(4), msk(4), mxge(4), nfe(4), re(4), rl(4), sis(4), and txp(4).
The btpand(8) daemon from NetBSD has been added. This daemon provides support for Bluetooth Network Access Point (NAP), Group Ad-hoc Network (GN) and Personal Area Network User (PANU) profiles.
The jail(8) subsystem has been updated. Changes include:
Multiple addresses of both IPv4 and IPv6 per jail has been supported. It is even possible to have jails without an IP address at all, which basically gives one a chrooted environment with restricted process view and no networking.
SCTP (sctp(4)) with IPv6 in jails has been implemented.
Specific CPU binding by using cpuset(1) has been implemented. Note that the current implementation allows the superuser inside of the jail to change the CPU bindings specified. This behavior will be fixed in the next release.
A jail(8) can start with a specific route FIB now.
A show jails subcommand in ddb(8) has been added.
Compatibility support which permits 32-bit jail binaries to be used on 64-bit systems to manage jails has been added.
Note that both version numbers of jail and prison in the jail(8) have been updated for the new features.
The supported version of the GNOME desktop environment (x11/gnome2) has been updated from 2.22 to 2.26.
The supported version of the KDE desktop environment has been updated from 3.5.10 (x11/kde3) to 4.2.2 (x11/kde4).
For more details, please see the
+ For more details, please see the
Detailed Release Notes. A list of all platforms currently under development can be found
- on the Supported
+ on the Supported
Platforms page. This is a specific schedule for the release of FreeBSD 7.2. For
more general information about the release engineering process,
- please see the Release
+ please see the Release
Engineering section of the web site. General discussions about the pending release and known issues should be
sent to the public
freebsd-stable mailing list.
- MFC
+ MFC
requests should be sent to
re@FreeBSD.org.
++++
diff --git a/website/content/en/releases/7.2R/schedule.adoc b/website/content/en/releases/7.2R/schedule.adoc
index 83e8b26cee..a3abf647d6 100644
--- a/website/content/en/releases/7.2R/schedule.adoc
+++ b/website/content/en/releases/7.2R/schedule.adoc
@@ -1,195 +1,195 @@
---
title: "FreeBSD 7.2 Release Process"
sidenav: download
---
++++
Introduction
Schedule
| Action | Expected | Actual | Description |
| Reminder announcement | 16 March 2009 | 17 March 2009 | Release Engineers send announcement email to developers with a rough schedule for the FreeBSD 7.2 release. |
| Announce the Ports Freeze | 3 April 2009 | 3 April 2009 | 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 | 23 March 2009 | 23 March 2009 | After this date, all commits to RELENG_7 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 | -- | 3 April 2009 | Notification of the impending doc/ tree slush should be sent to doc@. |
| Ports tree frozen | 13 April 2009 | 13 April 2009 | Only approved commits will be permitted to the ports/ tree during the freeze. |
| doc/ tree slush | 10 April 2009 | 10 April 2009 | 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. | 17 April 2009 | 17 April 2009 | Version number bumps for doc/ subtree. RELEASE_7_2_0 tag for doc/. doc/ slush ends at this time. |
| BETA1 builds | 30 March 2009 | 31 March 2009 | Begin BETA1 builds. |
| RELENG_7_2 branch | 10 April 2009 | 15 April 2009 | The new release branch is created. Update newvers.sh and release.ent on various branches involved. |
| RC1 builds | 13 April 2009 | 15 April 2009 | Begin RC1 builds. |
| Ports tree tagged | 20 April 2009 | 21 April 2009 | RELEASE_7_2_0 tag for ports/. |
| Ports tree unfrozen | 20 April 2009 | 21 April 2009 | After the ports/ tree is tagged, the ports/ tree will be re-opened for commits, but commits made after tagging will not go in 7.2-RELEASE. |
| Final package build starts | 20 April 2009 | 21 April 2009 | The ports cluster and pointyhat build final packages. |
| RC2 builds | 20 April 2009 | 23 April 2009 | Begin RC2 builds. |
| RELEASE builds | 1 May 2009 | 1 May 2009 | Begin RELEASE builds. |
| Announcement | 4 May 2009 | 4 May 2009 | Announcement sent out after a majority of the mirrors have received the bits. |
| Turn over to the secteam | TBD | -- | RELENG_7_2 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The highlights in the 7.3-RELEASE are the following:
The ZFS file system has been updated to version 13. The changes include ZFS operations by a regular user, L2ARC, ZFS Intent Log on separated disks (slog), sparse volumes, and so on.
A lock handling error has been fixed in interaction between malloc(3) implementation and threading library.
A deadlock in the sched_ule(4) scheduler has been fixed.
A new sysctl variable security.bsd.map_at_zero has been added
and set to 1 (allow) by default. This
controls whether FreeBSD allows to map an object at the
address 0, which is part of the
user-controlled portion of the virtual address
space. Disabling this has some effect on preventing an attack
which injects malicious code into that location and triggers a
NULL pointer dereference in the kernel.
A new boot loader gptzfsboot, which supports GPT and ZFS has been added. zfsloader, the final boot loader similar to loader(8) which supports ZFS has been added.
[amd64, i386] CPU cache flushing has been optimized when changing caching attributes of pages by doing nothing for CPUs that support self-snooping and using CLFLUSH instead of a full cache invalidate when possible.
The amdsbwd(4) driver for AMD SB600/SB7xx watchdog timer has been added.
[amd64, i386] The hwpmc(4) driver for Hardware Performance Monitoring Counter support has been added.
DRM now supports Radeon HD 4200 (RS880), 4770 (RV740), and R6/7xx 3D, and Intel G41 chips.
The alc(4) driver for Atheros AR8131/AR8132 PCIe Ethernet controller has been added.
[sparc64] The cas(4) driver has been added to provide support for Sun Cassini/Cassini+ and National Semiconductor DP83065 Saturn Gigabit Ethernet devices.
A userland utility mfiutil(8) for the mfi(4) devices has been added.
A userland utility mptutil(8) for the mpt(4) devices has been added.
The yp(8) utilities now support shadow.byname and shadow.byuid maps. These requires privileged port access.
The service(8) command as an easy interface for the rc.d scripts has been added.
ISC BIND has been updated to version 9.4-ESV.
sendmail has been updated from version 8.14.3 to version 8.14.4.
The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.28.2.
The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.3.5.
FreeBSD release ISO images now have “FreeBSD-” at the beginning of the filenames.
For more details, please see the
+ For more details, please see the
Detailed Release Notes. A list of all platforms currently under development can be found
- on the Supported
+ on the Supported
Platforms page. This is a specific schedule for the release of FreeBSD 7.3. For
more general information about the release engineering process,
- please see the Release
+ please see the Release
Engineering section of the web site. General discussions about the pending release and known issues should be
sent to the public
freebsd-stable mailing list.
- MFC
+ MFC
requests should be sent to re@FreeBSD.org.
++++
diff --git a/website/content/en/releases/7.3R/schedule.adoc b/website/content/en/releases/7.3R/schedule.adoc
index c72512e079..148954381a 100644
--- a/website/content/en/releases/7.3R/schedule.adoc
+++ b/website/content/en/releases/7.3R/schedule.adoc
@@ -1,154 +1,154 @@
---
title: "FreeBSD 7.3 Release Process"
sidenav: download
---
++++
Introduction
Schedule
| Action | Expected | Actual | Description |
| Release schedule announcement | — | 23 January 2010 | Release Engineers send announcement email to freebsd-stable@ with a rough schedule for the FreeBSD 7.3 release. |
| Code freeze begins | 22 January 2010 | 23 January 2010 | After this date, all commits to RELENG_7 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. |
| BETA1 builds | 25 January 2010 | 27 January 2010 | Begin BETA1 builds. |
| Announce doc/ tree slush | — | 31 January 2010 | Notification of the impending doc/ tree slush should be sent to doc@. |
| doc/ tree slush | 5 February 2010 | 5 February 2010 | 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. | 10 February 2010 | 10 February 2010 | Version number bumps for doc/ subtree. RELEASE_7_3_0 tag for doc/. doc/ slush ends at this time. |
| Ports tree feature freeze | 8 February 2010 | 15 February 2010 | Only feature safe commits will be permitted to the ports/ tree during the freeze. |
| RELENG_7_3 branch | — | 10 February 2010 | The new release branch is created. Update newvers.sh and release.ent on various branches involved. |
| RC1 builds | 8 February 2010 | 10 February 2010 | Begin RC1 builds. |
| RC2 builds | 22 February 2010 | 1 March 2010 | Begin RC2 builds. |
| RELENG_7_3_0_RELEASE tagged | — | 21 March 2010 | The release tag for 7.3-RELEASE is set on RELENG_7_3 branch. |
| RELEASE builds | — | 21 March 2010 | Begin RELEASE builds. |
| Announcement | 23 March 2010 |
23 March 2010 | Announcement sent out after a majority of the mirrors have received the bits. |
This is the release schedule for FreeBSD 7.4. For more - information about the release engineering process, please see the Release Engineering section of the + information about the release engineering process, please see the Release Engineering section of the web site.
General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. - MFC + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 08 October 2010 | Release Engineers send announcement email to developers with a rough schedule. |
| Release schedule reminder | - | Weekly | Release Engineers send reminder announcement e-mail to developers with updated schedule. |
| Code freeze begins | 28 November 2010 | 29 November 2010 | Release Engineers announce that all further commits to the stable/7 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc. |
| BETA1 | 03 December 2010 | 10 December 2010 | First beta test snapshot. |
| releng/7.4 branch | 15 December 2010 | 21 December 2010 | Subversion branch created, propagated to CVS; future release engineering proceeds on this branch. |
| RC1 | 17 December 2010 | 26 December 2010 | First release candidate. |
| RC2 | 07 January 2011 | 22 January 2011 | Second release candidate. |
| RC3 | 28 January 2011 | 03 February 2011 | Third release candidate. |
| RELEASE build | 21 January 2011 | - | 7.4-RELEASE built. |
| RELEASE announcement | 24 January 2011 | - | 7.4-RELEASE press release. |
| Turn over to the secteam | 31 January 2011 | - | RELENG_7_4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The FreeBSD Release Engineering Team is pleased to announce the availability of FreeBSD 8.0-RELEASE. This release starts off the new 8-STABLE branch which improves on the functionality of FreeBSD 7.X and introduces many new features. Some of the highlights:
Xen Dom-U, VirtualBox guest and host, hierarchical jails.
NFSv3 GSSAPI support, experimental NFSv4 client and server.
802.11s D3.03 wireless mesh networking and Virtual Access Point support.
ZFS is no longer in experimental status.
Ground-up rewrite of USB, including USB target support.
Continued SMP scalability improvements in many areas, especially VFS.
Revised network link layer subsystem.
Experimental MIPS architecture support.
The press release contains more +
The press release contains more information on this release.
For a complete list of new features and known problems, please see the online release notes and errata list available at:
For more information about FreeBSD release engineering activities please see:
The FreeBSD Project dedicates this release to the memories of Jean-Marc Zucconi (jmz@) and John Birrell (jb@) who passed away in May and November of 2009 respectively. Jean-Marc and John were both FreeBSD committers since the mid-1990s and made extensive contributions to the operating system. They will be missed.
FreeBSD 8.0-RELEASE is now available for the amd64, i386, ia64, pc98, powerpc, and sparc64 architectures.
FreeBSD 8.0 can be installed from bootable ISO images or over the network. Some architectures (currently amd64 and i386) also support installing from a USB memory stick. The required files can be downloaded via FTP or BitTorrent as described in the sections below. While some of the smaller FTP mirrors may not carry all architectures, they will all generally contain the more common ones such as amd64 and i386.
MD5 and SHA256 hashes for the release ISO and memory stick images are included at the bottom of this message.
The purpose of the images provided as part of the release are as follows:
This contains everything necessary to install the base FreeBSD operating system, a collection of pre-built packages, and the documentation. It also supports booting into a "livefs" based rescue mode. This should be all you need if you can burn and use DVD-sized media.
This contains the base FreeBSD operating system and the documentation packages for CDROM-sized media. There are no other packages.
This contains support for booting into a "livefs" based rescue mode but does not support doing an install from the CD itself. It is meant to help rescue an existing system but could be used to do a network based install if necessary.
This supports booting a machine using the CDROM drive but does not contain the support for installing FreeBSD from the CD itself. You would need to perform a network based install (e.g. from an FTP server) after booting from the CD.
This can be written to an USB memory stick (flash drive) and used to do an install on machines capable of booting off USB drives. It also supports booting into a "livefs" based rescue mode. The documentation packages are provided but no other packages.
As one example of how to use the memstick image, assuming the USB drive appears as /dev/da0 on your machine something like this should work:
# dd if="8".0-RELEASE-amd64-memstick.img of=/dev/da0 bs="10240" conv="sync"
Be careful to make sure you get the target (of=) correct.
FreeBSD 8.0-RELEASE can also be purchased on CD-ROM or DVD from several vendors. One of the vendors that will be offering FreeBSD 8.0-based products is:
FreeBSD Mall, Inc. http://www.freebsdmall.com/
8.0-RELEASE ISOs are available via BitTorrent. A collection of torrent files to download the images is available at:
At the time of this announcement the following FTP sites have FreeBSD 8.0-RELEASE available.
However before trying these sites please check your regional mirror(s) first by going to:
ftp://ftp.<yourdomain>.FreeBSD.org/pub/FreeBSD
Any additional mirror sites will be labeled ftp2, ftp3 and so on.
More information about FreeBSD mirror sites can be found at:
For instructions on installing FreeBSD, please see Chapter 2 of The FreeBSD Handbook. It provides a complete installation walk-through for users new to FreeBSD, and can be found online at:
The procedure for doing a source code based update is described in the FreeBSD Handbook:
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/synching.html
http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/makeworld.html
The branch tag to use for updating the source is RELENG_8_0.
The freebsd-update(8) utility supports binary upgrades of i386 and amd64 systems running earlier FreeBSD releases. Systems running 7.[012]-RELEASE, 8.0-BETA[1234], or 8.0-RC[123] can upgrade as follows:
# freebsd-update upgrade -r 8.0-RELEASE
During this process, FreeBSD Update may ask the user to help by merging some configuration files or by confirming that the automatically performed merging was done correctly.
# freebsd-update install
The system must be rebooted with the newly installed kernel before continuing.
# shutdown -r now
After rebooting, freebsd-update needs to be run again to install the new userland components:
# freebsd-update install
At this point, users of systems being upgraded from FreeBSD 8.0-BETA2 or earlier will be prompted by freebsd-update to rebuild all third-party applications (e.g., ports installed from the ports tree) due to updates in system libraries. See:
for more details. After updating installed third-party applications (and again, only if freebsd-update printed a message indicating that this was necessary), run freebsd-update again so that it can delete the old (no longer used) system libraries:
# freebsd-update install
Finally, reboot into 8.0-RELEASE:
# shutdown -r now
The FreeBSD Security Team currently plans to support FreeBSD 8.0 until November 30th, 2010. For more information on the Security Team and their support of the various FreeBSD branches see:
Many companies donated equipment, network access, or man-hours to support the release engineering activities for FreeBSD 8.0 including The FreeBSD Foundation, Hewlett-Packard, Yahoo!, NetApp, Internet Systems Consortium, and Sentex Communications.
The release engineering team for 8.0-RELEASE includes:
| Ken Smith <kensmith@FreeBSD.org> | Release Engineering, amd64, i386, sparc64 Release Building, Mirror Site Coordination |
| Robert Watson <rwatson@FreeBSD.org> | Release Engineering, Security |
| Konstantin Belousov <kib@FreeBSD.org> | Release Engineering |
| Marc Fonvieille <blackend@FreeBSD.org> | Release Engineering, Documentation |
| George Neville-Neil <gnn@FreeBSD.org> | Release Engineering |
| Hiroki Sato <hrs@FreeBSD.org> | Release Engineering, Documentation |
| Bjoern Zeeb <bz@FreeBSD.org> | Release Engineering |
| Marcel Moolenaar <marcel@FreeBSD.org> | ia64, powerpc Release Building |
| Takahashi Yoshihiro <nyan@FreeBSD.org> | PC98 Release Building |
| Joe Marcus Clarke <marcus@FreeBSD.org> | Package Building |
| Erwin Lansing <erwin@FreeBSD.org> | Package Building |
| Mark Linimon <linimon@FreeBSD.org> | Package Building |
| Pav Lucistnik <pav@FreeBSD.org> | Package Building |
| Ion-Mihai Tetcu <itetcu@FreeBSD.org> | Package Building |
| Martin Wilke <miwi@FreeBSD.org> | Package Building |
| Colin Percival <cperciva@FreeBSD.org> | Security Officer |
FreeBSD is a registered trademark of The FreeBSD Foundation.
MD5 (8.0-RELEASE-amd64-bootonly.iso) = 49ccdac2e01b33c943ae89233c465ef1 MD5 (8.0-RELEASE-amd64-disc1.iso) = eba84fbd08133cbc8c9ed67be27ee0c8 MD5 (8.0-RELEASE-amd64-dvd1.iso) = 44c016ae8812a266f710d1845722366d MD5 (8.0-RELEASE-amd64-livefs.iso) = 8db54cfc97b2afa97fb13dbccace4bfa MD5 (8.0-RELEASE-amd64-memstick.img) = b4558fa30d13776988d86477e9631887
MD5 (8.0-RELEASE-i386-bootonly.iso) = aede8888c250b648bf799d508bc9bf9d MD5 (8.0-RELEASE-i386-disc1.iso) = ace0afedfa7c6e0ad12c77b6652b02ab MD5 (8.0-RELEASE-i386-dvd1.iso) = 5336cd827991e4d4cff6d73c4a5ca105 MD5 (8.0-RELEASE-i386-livefs.iso) = 7f4f0ab014f853c8a99c053c2dc12641 MD5 (8.0-RELEASE-i386-memstick.img) = 0a769af739a92f5f495d1a6842e8150b
MD5 (8.0-RELEASE-ia64-bootonly.iso) = be9dcfc2f638d5f86e21b0b344bec91b MD5 (8.0-RELEASE-ia64-disc1.iso) = e982547f376432d09be603b117f4da54 MD5 (8.0-RELEASE-ia64-disc2.iso) = 5bc7616212e6977c4f054a84ef538615 MD5 (8.0-RELEASE-ia64-disc3.iso) = cefe2fd4694f5065e55778f879dc5852 MD5 (8.0-RELEASE-ia64-dvd1.iso) = 6b8df7fb34d5960ecf91a291926a1e6f MD5 (8.0-RELEASE-ia64-livefs.iso) = fe7933f2c1ddc2f4a90d5dfc48c38995
MD5 (8.0-RELEASE-pc98-bootonly.iso) = 16a29c2e31025c02997de21aac5041bb MD5 (8.0-RELEASE-pc98-disc1.iso) = 58e423d5a0a69a72016ebbecde265abd MD5 (8.0-RELEASE-pc98-livefs.iso) = 6ad13607eb305338edd9501310e6699c
MD5 (8.0-RELEASE-powerpc-bootonly.iso) = f60f73d55100f664c635c6848f00c6d8 MD5 (8.0-RELEASE-powerpc-disc1.iso) = 1323203ffeb317f47219ed8927449980 MD5 (8.0-RELEASE-powerpc-disc2.iso) = 5967750bf681428d59070a133b272bfd MD5 (8.0-RELEASE-powerpc-disc3.iso) = 43e4846683ce43fa8d6158c703767635
MD5 (8.0-RELEASE-sparc64-bootonly.iso) = 75b2f04c29e6b81058944e42055fe604 MD5 (8.0-RELEASE-sparc64-disc1.iso) = f4aa61db620c97089641a0c63531225a MD5 (8.0-RELEASE-sparc64-dvd1.iso) = 85307705213a86a383e21941ee34d8e2 MD5 (8.0-RELEASE-sparc64-livefs.iso) = 1ff6d6a449975dcc829f328b866f8128
SHA256 (8.0-RELEASE-amd64-bootonly.iso) = b0e07e8f92303b61220cba18691e86ab50d67c7df974bb62a6f1d4ffb94a1ee6 SHA256 (8.0-RELEASE-amd64-disc1.iso) = 7d4583c20c651093b208170a7fd4ed5f38ee5af0cbe19fb742f67175a9fee10f SHA256 (8.0-RELEASE-amd64-dvd1.iso) = 408f7fdf3226d72564f2476fff365e4fd071bd48ddae26cd34755d808ad54b8b SHA256 (8.0-RELEASE-amd64-livefs.iso) = ae939a96b3b3691df84227a33de5d5f4a76d469379dca27114c3557ed443a8f3 SHA256 (8.0-RELEASE-amd64-memstick.img) = b6cd7b0644f636f2099820ad1250940975fa3bfc19f74a0a94f69e75cc2be4c2
SHA256 (8.0-RELEASE-i386-bootonly.iso) = 12e32cea29b2f7bf873df43321a1a93d45b48a6fbb37c8e1c7f3003d5ce82e5d SHA256 (8.0-RELEASE-i386-disc1.iso) = d7ef47a76a20a716c006a635b476ed3515830b8442ded2702ed015f0bde32bcf SHA256 (8.0-RELEASE-i386-dvd1.iso) = 8b7bc67599fffc443ebc08efae8a49dd4a0fed7512cfb02b963b9a218e7c286c SHA256 (8.0-RELEASE-i386-livefs.iso) = feb8998bf2b9dbd6ae86f24feb9ab3c25983dc62c9f4a27f6a5314c3a4a7b59a SHA256 (8.0-RELEASE-i386-memstick.img) = 7e9b9cd2fd7af0fa0715b826a034b83b0f732a544a51cac7539ead5522a08806
SHA256 (8.0-RELEASE-ia64-bootonly.iso) = c594debd1cb629bf4c906da79c4a6d47b24cf4836d7690f18bc42ee9e31b6b92 SHA256 (8.0-RELEASE-ia64-disc1.iso) = c7f4bd197ff9996ead66f4c77d077e115d18a2822e006bdfdc86a5824dcef37e SHA256 (8.0-RELEASE-ia64-disc2.iso) = bfcd99680bc15e1b66329a0e71eaf6b38b44d1909a3fb43ba5485238e6807dfd SHA256 (8.0-RELEASE-ia64-disc3.iso) = 8e8edea7117239af60c07c7e724567ea276fa32d8634f04dd30312e72b35df9a SHA256 (8.0-RELEASE-ia64-dvd1.iso) = bd1c9a3e8a6a287ee7bef62b3e15646d76a97dec3108177a7c606706a7ee9952 SHA256 (8.0-RELEASE-ia64-livefs.iso) = 60a9a7738ad94765cad45dbc4f62913dd728b335d22bb4e5b065c0cae40a99db
SHA256 (8.0-RELEASE-pc98-bootonly.iso) = 7df38839c8da226bca8ef18b00f0b680074267b8333a393c3431f9b620f0ab9f SHA256 (8.0-RELEASE-pc98-disc1.iso) = b41fb185b1e057ee36ae6e080021f309a379c3fdf5d45a0a40461092d31e052a SHA256 (8.0-RELEASE-pc98-livefs.iso) = 1313ec3d5a28af8a85c181cd702b2adb91c783db7e2ad2021d311686ce5e0c2d
SHA256 (8.0-RELEASE-powerpc-bootonly.iso) = 78e18d76c24c9636b87f1946f2020a0a58fc70b80bcb925c27fa497b3c9e5bb4 SHA256 (8.0-RELEASE-powerpc-disc1.iso) = 80f5c024b61629b77a73fd396917c68b4d0215019a5e5aaf5882cf14144764a2 SHA256 (8.0-RELEASE-powerpc-disc2.iso) = 28c8e62c10b42fe5fb1e7a2235a6decbddbbfece0535ea42174c7ac937735068 SHA256 (8.0-RELEASE-powerpc-disc3.iso) = e36db6e05b434a0256e977cab9e3eedb5984b2c45c400a14d7c69bbf4dda9065
SHA256 (8.0-RELEASE-sparc64-bootonly.iso) = 941b5e76a67960045040c268894b8666f5b7a8cbd2e9f98186f2618abb5bf431 SHA256 (8.0-RELEASE-sparc64-disc1.iso) = 2d0a74cf867fa34c5a073777cf2d8e2469906425c9a54068892bd2d58ac9c3c5 SHA256 (8.0-RELEASE-sparc64-dvd1.iso) = 482447b382fa50ffdc80e02a0cfd774e0eecf7d009e5b06864e8a4f828536876 SHA256 (8.0-RELEASE-sparc64-livefs.iso) = 7499ca1af16de7b3d431741b1551a4b59f277fda997d57cf2615155992beaef7
The highlights in the 8.0-RELEASE are the following:
A new virtualization container named “vimage” has been implemented. This is a jail with a virtualized instance of the FreeBSD network stack and can be created by using jail(8) command.
The FreeBSD netisr framework has been reimplemented for parallel threading support. This is a kernel network dispatch interface which allows device drivers (and other packet sources) to direct packets to protocols for directly dispatched or deferred processing. The new implementation supports up to one netisr thread per CPU, and several benchmarks on SMP machines show substantial performance improvement over the previous version.
The FreeBSD TTY layer has been replaced with a new one which has better support for SMP and robust resource handling. A tty now has own mutex and it is expected to improve scalability when compared to the old implementation based on the Giant lock.
[amd64, i386] The FreeBSD Linux emulation layer has been updated to version 2.6.16 and the default Linux infrastructure port is now emulators/linux_base-f10 (Fedora 10).
The FreeBSD GENERIC kernel now includes Trusted BSD MAC (Mandatory Access Control) support. No MAC policy module is loaded by default.
The FreeBSD USB subsystem has been reimplemented to support modern devices and better SMP scalability. The new implementation includes Giant-lock-free device drivers, a Linux compatibility layer, usbconfig(8) utility, full support for split transaction and isochronous transaction, and so on.
The FreeBSD CAM SCSI subsystem ( cam(4)) now includes experimental support for ATA/SATA/AHCI-compliant devices.
The shared vnode locking for pathname lookups in the VFS(9) subsystem has been improved.
The ZFS file system has been updated to version 13. The changes include ZFS operations by a regular user, L2ARC, ZFS Intent Log on separated disks (slog), sparse volumes, and so on.
The FreeBSD NFS subsystem now supports RPCSEC_GSS authentication on both the client and server.
The FreeBSD NFS subsystem now includes a new, experimental implementation with support for NFSv2, NFSv3, and NFSv4.
The wireless network support layer (net80211) now supports multiple BSS instances on the supported network devices.
The FreeBSD L2 address translation table has been reimplemented to reduce lock contention on parallel processing and simplify the routing logic.
The IGMPv3 and SSM (Source-Specific Multicast) including IPv6 SSM and MLDv2 have been added.
The ipsec(4) subsystem now supports NAT-Traversal (RFC 3948).
The GCC stack protection (also known as ProPolice) has been enabled in the FreeBSD base system.
The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.26.3.
The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.3.1.
For more details, please see the
+ For more details, please see the
Detailed Release Notes. A list of all platforms currently under development can be found
- on the Supported
+ on the Supported
Platforms page. This is the release schedule for FreeBSD 8.0. For more
- information about the release engineering process, please see the Release Engineering section of the
+ information about the release engineering process, please see the Release Engineering section of the
web site. General discussions about the pending release and known issues should be
sent to the public
freebsd-current mailing list.
- MFC
+ MFC
requests should be sent to
re@FreeBSD.org.
++++
diff --git a/website/content/en/releases/8.0R/schedule.adoc b/website/content/en/releases/8.0R/schedule.adoc
index 86049dbef6..1b98c7891f 100644
--- a/website/content/en/releases/8.0R/schedule.adoc
+++ b/website/content/en/releases/8.0R/schedule.adoc
@@ -1,168 +1,168 @@
---
title: "FreeBSD 8.0 Release Process"
sidenav: download
---
++++
Introduction
Schedule
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 29 March 2009 | Release Engineers send announcement email to developers with a rough schedule. |
| Release schedule reminder | - | 5 May 2009 | Release Engineers send reminder announcement e-mail to developers with updated schedule. |
| Code slush | 1 June 2009 | 1 June 2009 | Release Engineers announce a slowdown in feature development for the release -- developers are requested to coordinate any non-refinement changes or late-arriving features with the release engineering team. |
| Code freeze begins | 25 June 2009 | 27 June 2009 | Release Engineers announce that all further commits to the head (and forthcoming RELENG_8 branch) will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvmeents, etc. |
| BETA1 | 29 June 2009 | 6 July 2009 | First beta test snapshot. |
| BETA2 | 6 July 2009 | 17 July 2009 | Second beta test snapshot. |
| RELENG_8 branch | - | 3 August 2009 - in progress | Subversion branch created, propagated to CVS and Perforce; future release engineering proceeds on this branch although code freeze/ slush continue for some time on head. |
| BETA3 | 13 July 2009 | 24 August 2009 | Third beta test snapshot. |
| BETA4 | 5 September 2009 | 7 September 2009 | Begin BETA4 builds. |
| RC1 | 14 September 2009 | 21 September 2009 | First release candidate. |
| RC2 | 21 September 2009 | 28 October 2009 | Second release candidate. |
| RC3 | - | 12 November 2009 | Third release candidate. |
| RELEASE build | 28 September 2009 | 22 November 2009 | 8.0-RELEASE built. |
| RELEASE announcement | TBD | 25 November 2009 | 8.0-RELEASE press release. |
| Turn over to the secteam | TBD | 01 December 2009 | RELENG_8_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The highlights in the 8.1-RELEASE are the following:
[powerpc] FreeBSD now supports SMP in PowerPC G5 systems. Note that SMP support on FreeBSD/powerpc is disabled by default in GENERIC kernel.
[sparc64] FreeBSD now supports UltraSPARC IV, IV+, and SPARC64 V CPUs.
The ZFS zpool version has been updated to 14. The zfsloader has been added. This is a separate zfs(8) enabled loader. Note that a ZFS bootcode (zfsboot or gptzfsboot) need to be installed to use this new loader.
The bwn(4) driver for Broadcom BCM43xx chipsets has been added.
The run(4) driver for Ralink RT2700U/RT2800U/RT3000U USB 802.11agn devices has been added.
The sge(4) driver for Silicon Integrated Systems SiS190/191 Fast/Gigabit Ethernet has been added. This supports TSO and TSO over VLAN.
The uhso(4) driver for Option HSDPA USB devices has been added. A new uhsoctl(1) userland utility can be used to initiate and close the WAN connection.
The urtw(4) driver has been improved and now supports RTL8187B-based devices.
The ipfw(4) subsystem including dummynet(4) has been improved.
The pfil(9) framework for packet filtering in FreeBSD kernel now supports separate packet filtering instances like ipfw(4) for each VIMAGE jail.
The
vlan(4) pseudo
interface now supports TSO (TCP Segmentation Offloading). The capability flag is named as
IFCAP_VLAN_HWTSO and it is separated from IFCAP_VLAN_HWTAGGING. The
age(4),
alc(4),
ale(4),
bce(4),
bge(4),
cxgb(4),
jme(4), re(4), and
mxge(4) driver
support this feature.
The vlan(4) pseudo interface for IEEE 802.1Q VLAN now ignore renaming of the parent's interface name. The configured VLAN interfaces continue to work with the new name while previously the configurations were removed as the renaming happens.
The HAST (Highly Available STorage) framework has been added. This is a framework to allow transparently storing data on two physically separated machines connected over the TCP/IP network. HAST works in Primary-Secondary (Master-Backup, Master-Slave) configuration, which means that only one of the cluster nodes can be active at any given time. Only Primary node is able to handle I/O requests to HAST-managed devices. Currently HAST is limited to two cluster nodes in total.
FreeBSD
cam(3) SCSI
framework has been improved and a new kernel option option ATA_CAM has been added. This
turns
ata(4) controller
drivers into
cam(4) interface
modules. When enabled, this option deprecates all
ata(4) peripheral
drivers and interfaces such as ad
and acd, and allows
cam(4) drivers ada, and cd
and interfaces to be natively used instead. Note that this
is not enabled by default in the GENERIC kernel.
The mvs(4) CAM ATA driver for Marvell 88SX50XX/88SX60XX/88SX70XX/SoC SATA controllers has been added. This driver supports same hardware as the ata(4) driver does, but provides many additional features, such as NCQ and PMP.
The liblzma library for LZMA2 lossless data compression algorithm and the userland utilities xz(1), xzdec(1), lzma(1), and lzmainfo(1). has been imported.
The ACPI-CA has been updated to 20100304.
ISC BIND has been updated to version 9.6.2-P2.
OpenSSH has been updated from version 5.1p1 to version 5.4p1.
OpenSSL has been updated to version 0.9.8n.
sendmail has been updated to version 8.14.4.
The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.28.2.
The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.4.3.
For more details, please see the
+ For more details, please see the
Detailed Release Notes. A list of all platforms currently under development can be found
- on the Supported
+ on the Supported
Platforms page. This is the release schedule for FreeBSD 8.1. For more
- information about the release engineering process, please see the Release Engineering section of the
+ information about the release engineering process, please see the Release Engineering section of the
web site. General discussions about the pending release and known issues should be
sent to the public
freebsd-current mailing list.
- MFC
+ MFC
requests should be sent to
re@FreeBSD.org.
++++
diff --git a/website/content/en/releases/8.1R/schedule.adoc b/website/content/en/releases/8.1R/schedule.adoc
index 7d8c239b22..d06360ad1b 100644
--- a/website/content/en/releases/8.1R/schedule.adoc
+++ b/website/content/en/releases/8.1R/schedule.adoc
@@ -1,129 +1,129 @@
---
title: "FreeBSD 8.1 Release Process"
sidenav: download
---
++++
Introduction
Schedule
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 01 April 2010 | Release Engineers send announcement email to developers with a rough schedule. |
| Release schedule reminder | - | Weekly | Release Engineers send reminder announcement e-mail to developers with updated schedule. |
| Code freeze begins | 24 May 2010 | 25 May 2010 | Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc. |
| BETA1 | 28 May 2010 | 27 May 2010 | First beta test snapshot. |
| releng/8.1 branch | 10 June 2010 | 14 June 2010 | Subversion branch created, propagated to CVS; future release engineering proceeds on this branch. |
| RC1 | 11 June 2010 | 14 June 2010 | First release candidate. |
| RC2 | 25 June 2010 | 26 June 2010 | Second release candidate. |
| RELEASE build | 09 July 2010 | 17 July 2010 | 8.1-RELEASE built. |
| RELEASE announcement | TBD | 23 July 2010 | 8.1-RELEASE press release. |
| Turn over to the secteam | TBD | 30 July 2010 | RELENG_8_1 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
The highlights in the 8.2-RELEASE are the following:
[amd64] FreeBSD/amd64 now always sets the KVA space as equal to or larger than physical memory size. This change would help to prevent a “kmem_map too small” panic which often occurs when using ZFS.[r214620]
The FreeBSD GENERIC kernel is now
compiled with KDB and KDB_TRACE options. From 8.2-RELEASE
the kernel supports displaying a stack trace on panic by
using
stack(9) facility
with no debugger backend like
ddb(8). Note that
this does not change the default behaviors of the GENERIC kernel on panic.[r214326]
The FreeBSD crypto(4) framework (opencrypto) now supports XTS-AES (XEX-TCB-CTS, or XEX-based Tweaked Code Book mode with CipherText Stealing), which is defined in IEEE Std. 1619-2007.[r214254]
[amd64] Xen HVM support in FreeBSD/amd64 kernel has been improved. For more details, see xen(4) manual page.[r215788]
FreeBSD now fully supports GPT (GUID Partition Table). Checksums of primary header and primary partition table are verified properly now.[r213994]
[amd64, i386] The aesni(4) driver has been added. This supports AES accelerator on Intel CPUs and accelerates AES operations for crypto(4).[r215633]
[amd64, i386] The aibs(4) driver has been added. This supports the hardware sensors in ASUS motherboards and replaces the acpi_aiboost(4) driver.[r210476]
The tpm(4) driver, which supports Trusted Platform Module has been added.[r215036]
The xhci(4) driver, which supports Extensible Host Controller Interface (xHCI) and USB 3.0, has been added.[r215944]
The FreeBSD Linux emulation subsystem now supports the video4linux API. This requires native video4linux hardware drivers such as the ones provided by multimedia/pwcbsd and multimedia/webcamd.
The miibus(4) has been rewritten for the generic IEEE 802.3 annex 31B full duplex flow control support. The alc(4), bge(4), bce(4), cas(4), fxp(4), gem(4), jme(4), msk(4), nfe(4), re(4), stge(4), and xl(4) drivers along with atphy(4), bmtphy(4), brgphy(4), e1000phy(4), gentbi(4), inphy(4), ip1000phy(4), jmphy(4), nsgphy(4), nsphyter(4), and rgephy(4) have been updated to support flow control via this facility.[r211379, r215881, r215890, r2105894, r216002, r216023, r216029, r216031, r216033]
A new netgraph(4) node ng_patch(4) has been added. This performs data modification of packets passing through. Modifications are restricted to a subset of C language operations on unsigned integers of 8, 16, 32 or 64-bit size.[r209843]
The FreeBSD TCP reassembly implementation has been improved. A long-standing
accounting bug affecting SMP systems has been fixed and the net.inet.tcp.reass.maxqlen
sysctl(8)
variable has been retired in favor of a per-connection dynamic limit based on the receive
socket buffer size. FreeBSD receivers now handle packet loss (particularly losses caused
by queue overflows) significantly better than before which improves connection
throughput.[r214865, r214866]
The siftr(4), Statistical Information For TCP Research (SIFTR) kernel module has been added. This is a facility that logs a range of statistics on active TCP connections to a log file. It provides the ability to make highly granular measurements of TCP connection state, aimed at system administrators, developers and researchers.[r214859]
The geli(8) GEOM class now uses XTS-AES mode by default.[r214405]
The ZFS on-disk format has been updated to version 15 and various performance improvements for the ZFS have been imported from OpenSolaris.
Userland support for the dtrace(1) subsystem has been added. This allows inspection of userland software itself and its correlation with the kernel, thus allowing a much better picture of what exactly is going on behind the scenes. The dtruss(1) utility has been added and libproc has been updated to support the facility.[r214983]
The gpart(8) utility now supports a recover subcommand for GPT partition tables.
The gpart(8) utility now supports GPT_ENT_ATTR_BOOTME, GPT_ENT_ATTR_BOOTONCE, and GPT_ENT_ATTR_BOOTFAILED attributes in GPT. The attribute keywords in the command line are bootme, bootonce, and bootfailed respectively.[r213994]
The libarchive library and tar(1) utility now support LZMA (Lempel-Ziv-Markov chain-Algorithm) compression format.[r213667]
The
newsyslog(8) utility now
supports an -S pidfile option to override the
default
syslogd(8) PID file.[r211699]
The newsyslog(8) utility now supports a special log file name <include> for processing file inclusion. Globbing in the file name and circular dependency detection are supported. For more details, see the newsyslog.conf(5) manual page.[r215622]
The pmcstat(8) utility now supports a file and a network socket as a top source. This allows top monitoring over TCP on a system with no local symbols, for example.[r211098]
The tftp(1) and tftpd(8) utilities have been improved for better interoperability and they now support RFC 1350, 2347, 2348, 2349, and 3617.[r213036, r213038]
A periodic script for zfs scrub has been added. For more details, see the periodic.conf(5) manual page.
A periodic script which can be used to find installed ports' files with mismatched checksum has been added. For more details, see the periodic.conf(5) manual page.
The sysinstall(8) utility now uses the following numbers for default and minimum partition sizes: 1GB for /, 4GB for /var, and 1GB for /tmp.[r211007]
The ACPI-CA has been updated to 20101013.
The ee(1) program has been updated to version 1.5.2.[r214287]
ISC BIND has been updated to version 9.6-ESV-R3.
netcat has been updated to version 4.8.
OpenSSL has been updated to version 0.9.8q.
The timezone database has been updated to the tzdata2010o release.
The xz has been updated from snapshot as of 12 April 2010 to 5.0.0 release
The supported version of the GNOME desktop environment (x11/gnome2) has been updated to 2.32.1.
The supported version of the KDE desktop environment (x11/kde4) has been updated to 4.5.5.
For more details, please see the
+ For more details, please see the
Detailed Release Notes. A list of all platforms currently under development can be found
- on the Supported
+ on the Supported
Platforms page. This is the release schedule for FreeBSD 8.2. For more
- information about the release engineering process, please see the Release Engineering section of the
+ information about the release engineering process, please see the Release Engineering section of the
web site. General discussions about the pending release and known issues should be
sent to the public
freebsd-stable mailing list.
- MFC
+ MFC
requests should be sent to
re@FreeBSD.org.
++++
diff --git a/website/content/en/releases/8.2R/schedule.adoc b/website/content/en/releases/8.2R/schedule.adoc
index a7e7f4d40d..a8c4e8d799 100644
--- a/website/content/en/releases/8.2R/schedule.adoc
+++ b/website/content/en/releases/8.2R/schedule.adoc
@@ -1,136 +1,136 @@
---
title: "FreeBSD 8.2 Release Process"
sidenav: download
---
++++
Introduction
Schedule
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 08 October 2010 | Release Engineers send announcement email to developers with a rough schedule. |
| Release schedule reminder | - | Weekly | Release Engineers send reminder announcement e-mail to developers with updated schedule. |
| Code freeze begins | 28 November 2010 | 29 November 2010 | Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc. |
| BETA1 | 03 December 2010 | 10 December 2010 | First beta test snapshot. |
| releng/8.2 branch | 15 December 2010 | 21 December 2010 | Subversion branch created, propagated to CVS; future release engineering proceeds on this branch. |
| RC1 | 17 December 2010 | 26 December 2010 | First release candidate. |
| RC2 | 07 January 2011 | 16 January 2011 | Second release candidate. |
| RC3 | 28 January 2011 | 03 February 2011 | Third release candidate. |
| RELEASE build | 21 January 2011 | - | 8.2-RELEASE built. |
| RELEASE announcement | 24 January 2011 | - | 8.2-RELEASE press release. |
| Turn over to the secteam | 31 January 2011 | - | RELENG_8_2 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
Important: All users are encouraged to consult the release errata before installing FreeBSD or submitting a problem report. The errata document is updated with late-breaking information discovered late in the release cycle or after the release. Typically, it contains information on known bugs, security advisories, and corrections to documentation. An up-to-date copy of the errata for FreeBSD 8.3-RELEASE can be found on the FreeBSD Web site.
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is the release schedule for FreeBSD 8.3. For more - information about the release engineering process, please see the Release Engineering section of the + information about the release engineering process, please see the Release Engineering section of the web site.
General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list.
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 25 January 2012 | Release Engineers send announcement email to developers with a rough schedule. |
| Code freeze begins | 15 February 2012 | 15 February 2012 | Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc. |
| BETA1 | 17 February 2012 | 20 February 2012 | First beta test snapshot. |
| releng/8.3 branch | - | 3 March 2012 | Subversion branch created, propagated to CVS; future release engineering proceeds on this branch. |
| RC1 | 02 March 2012 | 06 March 2012 | First release candidate. |
| RC2 | 16 March 2012 | 2 April 2012 | Second release candidate. |
| RELEASE build | 9 April 2012 | 9 April 2012 | 8.3-RELEASE build. |
| RELEASE announcement | - | 18 April 2012 | 8.3-RELEASE press release. |
| Turn over to the secteam | - | - | releng/8.3 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
Important: All users are encouraged to consult the release errata before installing FreeBSD or submitting a problem report. The errata document is updated with late-breaking information discovered late in the release cycle or after the release. Typically, it contains information on known bugs, security advisories, and corrections to documentation. An up-to-date copy of the errata for FreeBSD 8.4-RELEASE can be found on the FreeBSD Web site.
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is the release schedule for FreeBSD 8.4. For more - information about the release engineering process, please see the Release Engineering section of the + information about the release engineering process, please see the Release Engineering section of the web site.
General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list.
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 08 February 2013 | Release Engineers send announcement email to developers with a rough schedule. |
| Announce doc/ tree slush | - | 28 February 2013 | Notification of the impending doc/ tree slush should be sent to doc@. |
| Code freeze begins | 08 March 2013 | 08 March 2013 | Release Engineers announce that all further commits to the stable/8 branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc. |
| BETA1 | 20 March 2013 | 22 March 2013 | First beta test snapshot. |
| doc/ tree slush | 17 March 2013 | 17 March 2013 | 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. |
| ports/ tree freeze | 30 March 2013 | 30 March 2013 | Only security updates and critical fixes will be allowed to the tree during this freeze. |
| releng/8.4 branch | 18 March 2013 | 28 March 2013 | Subversion branch created, propagated to CVS; future release engineering proceeds on this branch. |
| RC1 | 30 March 2013 | 10 April 2013 | First release candidate. |
| RC2 | 21 April 2013 | 22 April 2013 | Second release candidate. |
| RC3 | 30 April 2013 | 8 May 2013 | Third release candidate. |
| RELEASE build | 02 June 2013 | 02 June 2013 | 8.4-RELEASE build. |
| RELEASE announcement | 07 June 2013 | 07 June 2013 | 8.4-RELEASE press release. |
| Turn over to the secteam | - | 16 June 2013 | releng/8.4 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |
Important: If you are upgrading from a previous release of FreeBSD, please read upgrading section in the Release Notes for notable incompatibilities carefully.
The highlights in the 9.0-RELEASE are the following. For more - details, please see the Detailed + details, please see the Detailed Release Notes.
The FreeBSD kernel now supports Capsicum Capability Mode. Capsicum is a set of features for sandboxing support, using a capability model in which the capabilities are file descriptors. Two new kernel options CAPABILITIES and CAPABILITY_MODE have been added to the GENERIC kernel. For more information about Capsicum, see http://www.cl.cam.ac.uk/research/security/capsicum/.[r219129]
The hhook(9) (Helper Hook) and khelp(9) (Kernel Helpers) KPIs have been implemented. These are a kind of superset of pfil(9) framework for more general use in the kernel. The hhook(9) KPI provides a way for kernel subsystems to export hook points that khelp(9) modules can hook to provide enhanced or new functionality to the kernel. The khelp(9) KPI provides a framework for managing khelp(9) modules, which indirectly use the hhook(9) KPI to register their hook functions with hook points of interest within the kernel. These allow a structured way to dynamically extend the kernel at runtime in an ABI preserving manner.[r216758, r216615]
A new resource accounting API has been implemented. It can keep per-process, per-jail, and per-loginclass resource accounting information. Note that this is not built nor installed by default. To build and install them, specify options RACCT in the kernel configuration file and rebuild the base system as described in the FreeBSD Handbook.[r220137]
A new resource-limiting API has been implemented. It works in conjunction with the RACCT resource accounting implementation and takes user-configurable actions based on the set of rules it maintains and the current resource usage. The rctl(8) utility has been added to manage the rules in userland. Note that this is not built nor installed by default. To build and install them, specify options RCTL in the kernel configuration file and rebuild the base system as described in the FreeBSD Handbook.[r220163]
[powerpc] FreeBSD/powerpc now supports Sony Playstation 3 using the OtherOS feature available on firmwares 3.15 and earlier.[r217044]
[amd64, i386] The FreeBSD usb(4) subsystem now supports USB 3.0 by default.[r223098]
The FreeBSD usb(4) subsystem now supports USB packet filter. This allows to capture packets which go through each USB host controller. The implementation is almost based on bpf(4) code. The userland program usbdump(8) has been added.[r215649]
A bxe(4) driver for Broadcom NetXtreme II 10GbE controllers (BCM57710, BCM57711, BCM57711E) has been added.[r219647]
A cxgbe(4) driver for Chelsio T4 (Terminator 4) based 10Gb/1Gb adapters has been added.[r218794]
The em(4) driver has been updated to version 7.3.2.[r219753]
The igb(4) driver has been updated to version 2.2.5.[r223350]
The igb(4) driver now supports Intel I350 PCIe Gigabit Ethernet controllers.[r218530]
The ixgbe(4) driver has been updated to version 2.3.8.[r217593]
The re(4) driver now supports RTL8168E/8111E-VL PCIe Gigabit Ethernet controllers and RTL8401E PCIe Fast Ethernet controllers.[r217498, r218760]
A vte(4) driver for RDC R6040 Fast Ethernet controllers, which are commonly found on the Vortex86 System On a Chip, has been added.[r216829]
A vxge(4) driver for the Neterion X3100 10GbE Server/Storage adapter has been added.[r221167]
ipfw(8) now supports the call and return actions. Upon the call number action, the current rule number is saved in the internal stack and ruleset processing continues with the first rule numbered number or higher. The return action takes the rule number saved to internal stack by the latest call action and returns ruleset processing to the first rule with number greater than that saved number.[r223666]
For Infiniband support, OFED (OpenFabrics Enterprise Distribution) version 1.5.3 has been imported into the base system. Note that this is not built nor installed by default. To build and install them, specify WITH_OFED=yes in /etc/src.conf and rebuild the base system as described in the FreeBSD Handbook.[r219820]
The FreeBSD TCP/IP network stack now supports IPv4 prefixes with /31 as described in RFC 3021, “Using 31-Bit Prefixes on IPv4 Point-to-Point Links”.[r226572]
The FreeBSD TCP/IP network stack now supports the
mod_cc(9) pluggable
congestion control framework. This allows TCP congestion
control algorithms to be implemented as dynamically loadable
kernel modules. The following kernel modules are available
as of 9.0-RELEASE:
cc_chd(4) for the
CAIA-Hamilton-Delay algorithm,
cc_cubic(4) for the
CUBIC algorithm,
cc_hd(4) for the
Hamilton-Delay algorithm,
cc_htcp(4) for the
H-TCP algorithm,
cc_newreno(4) for
the NewReno algorithm, and
cc_vegas(4) for the
Vegas algorithm. The default algorithm can be set by a new
sysctl(8) variable
net.inet.tcp.cc.algorithm. The
value must be set to one of the names listed by net.inet.tcp.cc.available, and newreno is the default set at boot
time. For more detail, see the
mod_cc(4) and
mod_cc(9) manual
pages.[r216109, r216114, r216115, r218152, r218153, r218155]
An h_ertt(4) (Enhanced Round Trip Time) khelp(9) module has been added. This module allows per-connection, low noise estimates of the instantaneous RTT in the TCP/IP network stack with a robust implementation even in the face of delayed acknowledgments and/or TSO (TCP Segmentation Offload) being in use for a connection.[r217806]
A new tcp(4) socket option TCP_CONGESTION has been added. This allows to select or query the congestion control algorithm that the TCP/IP network stack will use for connections on the socket.[r218912]
The ng_netflow(4) netgraph(4) node now supports NetFlow version 9. A new export9 hook has been added for NetFlow v9 data. Note that data export can be done simultaneously in both version 5 and version 9.[r219183]
The geom_map(4) GEOM class has been added. This allows to generate multiple geom providers based on a hard-coded layout of a device with no explicit partition table such as embedded flash storage. For more information, see the geom_map(4) manual page.[r220559]
The graid(8) GEOM class has been added. This is a replacement of the ataraid(4) driver supporting various BIOS-based software RAID.[r219974]
A tws(4) driver for 3ware 9750 SATA+SAS 6Gb/s RAID controllers has been added.[r226115]
The FreeBSD Fast File System now supports softupdates
journaling. It introduces a intent log into a
softupdates-enabled file system which eliminates the need for
background
fsck(8) even on
unclean shutdown. This can be enabled in a per-filesystem
basis by using the -j flag of the
newfs(8) utility or
the -j enable option of the
tunefs(8)
utility. Note that the 9.0-RELEASE installer automatically
enables softupdates journaling for newly-created UFS file
systems.[r207141, r218726]
The FreeBSD Fast File System now supports the TRIM command when freeing data blocks. A
new flag -t in the
newfs(8) and
tunefs(8) utilities
sets the TRIM-enable flag for a file system. The TRIM-enable
flag makes the file system send a delete request to the
underlying device for each freed block. The TRIM command is specified as a Data Set
Management Command in the ATA8-ACS2 standard to carry the
information related to deleted data blocks to a device,
especially for a SSD (Solid-State Drive) for optimization.[r216796]
The FreeBSD NFS subsystem has been updated. The new
implementation supports NFS version 4 in addition to 2 and
3. The kernel options for the NFS server and client are
changed from NFSSERVER and NFSCLIENT to NFSD and NFSCL.
sysctl(8) variables
which start with vfs.nfssrv. have
been renamed to vfs.nfsd.. The
NFS server now supports vfs.nfsd.server_max_nfsvers and vfs.nfsd.server_min_nfsvers
sysctl(8) variables to
specify the maximum and the minimum NFS version number which
the server accepts. The default value is set to 3 and 2,
respectively.[r221124]
The FreeBSD ZFS subsystem has been updated to the SPA
(Storage Pool Allocator, also known as zpool) version 28. It
now supports data deduplication, triple parity RAIDZ (raidz3),
snapshot holds, log device removal, zfs diff, zpool split,
zpool import -F, and read-only
zpool import.[r219089]
An implementation of iconv()
API libraries and utilities which are standardized in Single
UNIX Specification has been imported. These are based on
NetBSD's Citrus implementation. Note that these are not built
nor installed by default. To build and install them, specify
WITH_ICONV=yes in /etc/src.conf and rebuild the base
system as described in the FreeBSD Handbook.[r219019]
A readline(3) API set has been imported into libedit. This is based on NetBSD's implementation and BSD licensed utilities now use it instead of GNU libreadline.[r220370]
The rtsold(8) and rtadvd(8) daemons now support the RDNSS and DNSSL options described in RFC 6106, “IPv6 Router Advertisement Options for DNS Configuration”. A rtadvctl(8) utility to control the rtadvd(8) daemon has been added.[r222732, r224006]
The
rtld(1) runtime
linker now supports shared objects as filters in ELF shared
libraries. Both standard and auxiliary filtering have been
supported. The
rtld(1) linker's
processing of a filter defers loading a filtee until a
filter symbol is referenced unless the LD_LOADFLTR environment variable is
defined or a -z loadfltr option was
specified when the filter was created.[r216695]
A bug in the tftpd(8) daemon has been fixed. It had an interoperability issue when transferring a large file.[r224536]
The utmp(5) user accounting database has been replaced by utmpx(3). User accounting utilities will now use utmpx database files exclusively. The wtmpcvt(1) utility can be used to convert wtmp files to the new format, making it possible to read them using the updated utilities.[r202188]
The zpool(8): utility now supports a zpool labelclear command. This allows to wipe the label data from a drive that is not active in a pool.[r224171]
A list of all platforms currently under development can be found - on the Supported + on the Supported Platforms page.
This is the release schedule for FreeBSD 9.0. For more - information about the release engineering process, please see the Release Engineering section of the + information about the release engineering process, please see the Release Engineering section of the web site.
General discussions about the pending release and known issues should be sent to the public freebsd-stable mailing list. - MFC + MFC requests should be sent to re@FreeBSD.org.
| Action | Expected | Actual | Description |
| Initial release schedule announcement | - | 19 April 2011 | Release Engineers send announcement email to developers with a rough schedule. |
| Release schedule reminder | - | 6 May 2011, 15 June 2011 |
Release Engineers send reminder announcement e-mail to developers with updated schedule. |
| Code freeze begins | 17 July 2011 | 18 July 2011 | Release Engineers announce that all further commits to the head branch will require explicit approval. Certain blanket approvals will be granted for narrow areas of development, documentation improvements, etc. |
| BETA1 | 20 July 2011 | 1 August 2011 | First beta test snapshot. |
| BETA2 | 3 August 2011 | 7 September 2011 | Second beta test snapshot. |
| releng/9.0 branch | 3 August 2011 | 10 November 2011 | Subversion branch created, propagated to CVS; future release engineering proceeds on this branch. |
| BETA3 | 17 August 2011 | 28 September 2011 | Third beta test snapshot. |
| RC1 | 24 August 2011 | 22 October 2011 | First release candidate. |
| RC2 | 31 August 2011 | 17 November 2011 | Second release candidate. |
| RC3 | - | 8 December 2011 | Third release candidate. |
| RELEASE build | 7 September 2011 | 3 January 2012 | 9.0-RELEASE built. |
| RELEASE announcement | - | 12 January 2012 | 9.0-RELEASE press release. |
| Turn over to the secteam | - | 16 February 2012 | RELENG_9_0 branch is handed over to the FreeBSD Security Officer Team in one or two weeks after the announcement. |