Fix up references to STABLE and CURRENT branches. A slight variation

on the patch in the PR.

PR:		48606
Submitted by:	Xin LI <delphij@frontfree.net>
This commit is contained in:
Bruce A. Mah 2003-02-25 16:43:59 +00:00
parent b64f0003ab
commit 4d8fa27d7a
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=16126

View file

@ -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.36 2003/02/17 19:05:15 scottl Exp $">
<!ENTITY date "$FreeBSD: www/en/releng/index.sgml,v 1.37 2003/02/18 17:34:26 bmah Exp $">
<!ENTITY email 're'>
<!ENTITY title "Release Engineering Information">
<!ENTITY % includes SYSTEM "../includes.sgml"> %includes;
@ -59,11 +59,11 @@ subtrees are not branched and not covered by this table.</p>
<td> Semi-Frozen </td>
<td> &contact.re; </td>
<td> Active development branch for -CURRENT. Commits to this
branch will be in 5.1-RELEASE and 5.0-STABLE. Sometime around
the release of 5.1-RELEASE or 5.2-RELEASE, we will branch RELENG_5 (for 5.0-STABLE) and this
branch will then be known at 6.0-CURRENT. With that in mind,
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
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.0-RELEASE a success.
months and focus on fixing bugs to make 5-STABLE a success.
Invasive commits to <tt>HEAD</tt> must be coordinated and approved
by &contact.re;.</td>
</tr>