Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 5 Nov 2004 16:16:07 -0800
From:      Brooks Davis <brooks@one-eyed-alien.net>
To:        FreeBSD-CURRENT <current@freebsd.org>
Subject:   Re: FreeBSD 6.0 and onwards
Message-ID:  <20041106001607.GA21665@odin.ac.hmc.edu>
In-Reply-To: <20041106000442.GA2738@laptoxa.toxa.lan>
References:  <418C0EED.1060301@freebsd.org> <20041106000442.GA2738@laptoxa.toxa.lan>

next in thread | previous in thread | raw e-mail | index | archive | help

--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sat, Nov 06, 2004 at 03:04:42AM +0300, Toxa wrote:
> On Fri, Nov 05, 2004 at 04:38:21PM -0700, Scott Long wrote:
> > So the current plan is to branch RELENG_6 (aka 6-STABLE) sometime around
> > May or June 2005.  That will begin a 1-3 month freeze and stabilization
> > process for the 6.0 release.  After that is released, we will do 6.1,
> > 6.2 and onwards at likely 4 month intervals.  In May/June 2006 we'll
> > look at doing RELENG_7, or we might wait until Nov/Dec 2006 (12 months
>=20
> Don't you think branching 6-STABLE (and, thus, getting 6.x RELEASEs)
> around June 2005 is too early for users which may be confused a bit with
> 4.x, 5.x, and 6.x releases. Now we know 4.x stands for "technologically
> outdated" but proven stability, and 5.x stands for new technology, new
> stable branch. In 2005, 4.x won't lost its actuality, 5.x will be in the
> mainstream (hopefully), and what new 6.x releases will be stands for?
> I think, there is no radically new technologies, any improvemens from
> 6-current could be MFC'ed to 5-stable, so why messing with 6.x releases
> so early?

6.x already contains a fair bit of work that would be inadvisable to
MFC.  If nothing else, the TTY renaming can't be merged to a STABLE
branch.

-- Brooks

--=20
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBjBfGXY6L6fI4GtQRAmjNAKCR00qNwXb4ldE6+tZ8GuTBkP4agQCghZmK
qJ3JX4VlHF9ta5/fQ0Ihyo0=
=3SDO
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041106001607.GA21665>