| Summary: | Update early-adopter post-4.10 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Documentation | Reporter: | Chris Pepper <pepper> | ||||
| Component: | Books & Articles | Assignee: | Hiroki Sato <hrs> | ||||
| Status: | Closed FIXED | ||||||
| Severity: | Affects Only Me | CC: | pepper | ||||
| Priority: | Normal | ||||||
| Version: | Latest | ||||||
| Hardware: | Any | ||||||
| OS: | Any | ||||||
| Attachments: |
|
||||||
|
Description
Chris Pepper
2004-06-07 04:50:18 UTC
Responsible Changed From-To: freebsd-www->hrs I'll handle this. In addition to the previous changes, section 5 (below) should be revised, in light of the revised plans at <http://www.freebsd.org/releases/4.10R/announce.html>: >FreeBSD 4.10 will become the first "Errata Branch". Release >branches for previous versions of FreeBSD would only have critical >security fixes applied. With FreeBSD 4.10 the scope of fixes will >be expanded to include local Denial of Service fixes as well as >other significant and well-tested fixes that may not represent >security issues. > >The current plans are for one more FreeBSD 4.X release which will >be FreeBSD 4.11-RELEASE. It is expected the upcoming FreeBSD 5.3 >release will have reached the maturity level most users will be >able to migrate to 5.X. Most developer resources continue to be >devoted to the 5.X branch. Chris Pepper >5 Plans for the 4-STABLE Branch > >It is important to note that even though releases are being made in >the 5.X series, support for 4.X releases will continue for some >time. Indeed, FreeBSD 4.8 was released two months after 5.0, in >April 2003, followed by 4.9, in October 2003. Future releases from >the 4-STABLE branch (if any) will depend on several factors. The >most important of these is the existence and stability of the >5-STABLE branch. If CURRENT is not sufficiently stable to allow the >creation of a 5-STABLE branch, this may require and permit more >releases from the 4-STABLE branch. Until the last declared release >on the 4-STABLE branch, new features may be merged from HEAD at the >discretion of developers, subject to existing release engineering >policies. > >To some extent, the release engineering team (as well as the >developer community as a whole) will take into account user demand >for future 4-STABLE releases. This demand, however, will need to be >balanced with release engineering resources (particularly >developers' time, computing resources, and mirror archive space). We >note that in general, the FreeBSD community (both users and >developers) has shown a preference for moving forward with new >features in the 5.X branch and beyond, due to the difficulty >involved in backporting (and maintaining) new functionality in 4.X. > >The Security Officer Team <security-officer@FreeBSD.org> will >continue to support releases made from the 4-STABLE branch in >accordance with their published policies, which can be found on the >Security page on the FreeBSD web site. Generally, the two most >recent releases from any branch will be supported with respect to >security advisories and security fixes. At its discretion, the team >may support other releases for specific issues. > >At this point, the release engineering team has no specific plans >for future releases from the 4-STABLE development branch. It seems >likely that any future releases (if any) from this branch will be >lightweight, ``point'' releases. These will probably carry 4.9.X >version numbers, to indicate that they are not intended to provide >large amount of new functionality compared to 4.9-RELEASE. In >general, these releases will emphasize security fixes, bug fixes, >and device driver updates (particularly to accommodate new hardware >easily supported by existing drivers). Major new features >(especially those requiring infrastructure support added in 5.X) >will probably not be added in these releases. -- Chris Pepper: <http://www.reppep.com/~pepper/> Rockefeller University: <http://www.rockefeller.edu/> Even though this may have been relevant in mid 2004, I suppose it is no longer. I Propose to close this issue. State Changed From-To: open->closed Sorry for the late response. The proposed changes were committed when this PR was submitted. Thank you for your submission! |