From owner-freebsd-current@FreeBSD.ORG Sat Nov 6 00:15:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D0AC616A515 for ; Sat, 6 Nov 2004 00:15:25 +0000 (GMT) Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4F2A43D4C for ; Sat, 6 Nov 2004 00:15:18 +0000 (GMT) (envelope-from brdavis@odin.ac.hmc.edu) Received: from odin.ac.hmc.edu (localhost.localdomain [127.0.0.1]) by odin.ac.hmc.edu (8.13.0/8.13.0) with ESMTP id iA60G7Ck022226 for ; Fri, 5 Nov 2004 16:16:07 -0800 Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.13.0/8.13.0/Submit) id iA60G7qo022225 for current@freebsd.org; Fri, 5 Nov 2004 16:16:07 -0800 Date: Fri, 5 Nov 2004 16:16:07 -0800 From: Brooks Davis To: FreeBSD-CURRENT Message-ID: <20041106001607.GA21665@odin.ac.hmc.edu> References: <418C0EED.1060301@freebsd.org> <20041106000442.GA2738@laptoxa.toxa.lan> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK" Content-Disposition: inline In-Reply-To: <20041106000442.GA2738@laptoxa.toxa.lan> User-Agent: Mutt/1.4.1i X-Virus-Scanned: by amavisd-new X-Spam-Status: No, hits=0.0 required=8.0 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on odin.ac.hmc.edu Subject: Re: FreeBSD 6.0 and onwards X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 06 Nov 2004 00:15:26 -0000 --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--