Stop pretending that there's a possibility of a 5-STABLE branch before
the 5.2 release cycle.
This commit is contained in:
parent
a965a0999d
commit
7081f51902
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16702
1 changed files with 2 additions and 2 deletions
|
@ -1,6 +1,6 @@
|
|||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" [
|
||||
<!ENTITY base CDATA "..">
|
||||
<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.45 2003/04/04 07:21:45 bmah Exp $">
|
||||
<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.46 2003/04/24 06:09:52 murray Exp $">
|
||||
<!ENTITY email 're'>
|
||||
<!ENTITY title "Release Engineering Information">
|
||||
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
|
||||
|
@ -63,7 +63,7 @@ subtrees are not branched and not covered by this table.</p>
|
|||
<td> &contact.re; </td>
|
||||
<td> Active development branch for -CURRENT. Commits to this
|
||||
branch will be in 5.1-RELEASE and 5-STABLE. Sometime around
|
||||
the release of 5.1-RELEASE or 5.2-RELEASE, we will branch RELENG_5 (for 5-STABLE) and this
|
||||
the release of 5.2-RELEASE, we will branch RELENG_5 (for 5-STABLE) and this
|
||||
branch will then be known at 6-CURRENT. With that in mind,
|
||||
developers should treat this as a "STABLE" branch for the next few
|
||||
months and focus on fixing bugs to make 5-STABLE a success.
|
||||
|
|
Loading…
Reference in a new issue