os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Oops. Forgot a branch name (RELENG_3).

Browse source
This commit is contained in:
Bruce A. Mah 2003-02-17 22:43:35 +00:00
parent ff1fde8ecf
commit 0620d65d90
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=16050
1 changed files with 4 additions and 3 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

7
en_US.ISO8859-1/articles/5-roadmap/article.sgml
View file

@ -14,6 +14,7 @@
<!ENTITY % mailing-lists PUBLIC "-//FreeBSD//ENTITIES DocBook Mailing List Entities//EN">
%mailing-lists;
<!ENTITY t.releng.3 "<literal>RELENG_3</literal>">
<!ENTITY t.releng.4 "<literal>RELENG_4</literal>">
<!ENTITY t.releng.5 "<literal>RELENG_5</literal>">
<!ENTITY t.releng.5.1 "<literal>RELENG_5_1</literal>">
@ -59,11 +60,11 @@
seemingly forever, and finally a cry was made to <quote>just ship it</quote> and
clean up later. This decision resulted in the 3.0 and 3.1 releases
being very unsatisfying for most, and it wasn't until 3.2 that the
series was considered <quote>stable</quote>. To make matters worse, the RELENG_3
series was considered <quote>stable</quote>. To make matters worse, the &t.releng.3;
branch was created along with the 3.0 release, and the &t.releng.head; branch was
allowed to advance immediately towards 4-CURRENT. This resulted in a
quick divergence between &t.releng.head; and RELENG_3, making maintenance of the
RELENG_3 branch very difficult. &os; 2.2.8 was left for quite a while
quick divergence between &t.releng.head; and &t.releng.3;, making maintenance of the
&t.releng.3; branch very difficult. &os; 2.2.8 was left for quite a while
as the last production-quality version of &os;.</para>
<para>Our intent is to avoid repeating that scenario with &os; 5.x.