From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 16434 invoked from network); 10 Aug 2004 14:11:05 +0000 Received: from smtp.gentoo.org (156.56.111.197) by lists.gentoo.org with AES256-SHA encrypted SMTP; 10 Aug 2004 14:11:05 +0000 Received: from lists.gentoo.org ([156.56.111.196] helo=parrot.gentoo.org) by smtp.gentoo.org with esmtp (Exim 4.34) id 1BuXLE-0005go-Fc for arch-gentoo-dev@lists.gentoo.org; Tue, 10 Aug 2004 14:11:04 +0000 Received: (qmail 14885 invoked by uid 89); 10 Aug 2004 14:11:03 +0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 18059 invoked from network); 10 Aug 2004 14:11:03 +0000 From: Chris Gianelloni Reply-To: wolf31o2@gentoo.org To: gentoo-dev@lists.gentoo.org In-Reply-To: <200408100826.35272.cshields@gentoo.org> References: <20040808185144.GB29077@mail.lieber.org> <20040810000107.GX29077@mail.lieber.org> <1092144188.21441.19.camel@localhost> <200408100826.35272.cshields@gentoo.org> Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-AaS2rjrjAGHXgSX5Oinl" Organization: Gentoo Linux Message-Id: <1092145722.21441.39.camel@localhost> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.6 Date: Tue, 10 Aug 2004 09:48:43 -0400 Subject: Re: [gentoo-dev] GLEP 19, reloaded (again) X-Archives-Salt: c9920359-1c30-48ef-807a-0d9da2d73c74 X-Archives-Hash: ab63ec2d4f36a042087edc633cf656b2 --=-AaS2rjrjAGHXgSX5Oinl Content-Type: text/plain Content-Transfer-Encoding: quoted-printable On Tue, 2004-08-10 at 09:26, Corey Shields wrote: > There is no release for this at all.. We can use the same release cd's t= hat=20 > are currently available. I still don't see the advantage of 2 release cycles. I honestly feel like our current quarterly release cycles are a bit ambitious. Adding any other release cycles into this mix would simply be overwhelming for our staff. > > So the idea is to create exactly *one* stable tree? How is this any > > different than just doing better with our current tree? Honestly, from > > what I've heard from our users, they want package stability (as in > > freeze) much more than anything else. This is *exactly* why I recommen= d > > tying the "stable" trees with the releases. I'm not sure I can > > understand how doing anything else really gives us anything other than > > adding more workload for the simple fact of adding workload. Having a > > "stable" tree that still moves, and only providing a single "stable" > > tree doesn't seem to be an improvement from what we have at all. >=20 > when we say "stable" we are talking about the package freeze you mention.= =20 > Some people want daily updates of stuff to be on the bleeding edge. This= is=20 > one of the biggest selling points of Gentoo, and should remain that way. = =20 > This project aims at making a tree (or however it is implemented) that do= es=20 > not change as often. For example, I don't need every little gcc and=20 > man-pages update on my production system. This would provide some stabil= ity=20 > to the tree. I guess that "stable" is a bad term here as it is easily=20 > confused for system stability. I guess when I hear stable, I think *UN*changing... not "changing less often". Adding "some" stability is not what our users are asking for from us. They are asking for a "stable" tree. A single tree cannot provide this. Having a "bleeding" and a "stable" tree cannot provide this. This is why I have always been pushing the idea of having a "release" tree which coincides with the release media. You then have a complete set of "stable" packages, both in the form of the release tree, and also in the form of pre-compiled binary GRP packages. It also would open up the possibility of creating binary-only update packages if we so desired to in the future. Installing from a Gentoo 2019.2 CD would then *always* produce an *identical* install, just as it does with any other distribution, and just like our users are requesting. This does not change the "gentoo-portage" module, which would be the equivalent of something like freebsd's or slackware's -current branches. --=20 Chris Gianelloni Release Engineering QA Manager/Games Developer Gentoo Linux Is your power animal a penguin? --=-AaS2rjrjAGHXgSX5Oinl Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (GNU/Linux) iD8DBQBBGNI6kT4lNIS36YERAsfWAJ95BFGv6UcFh8IB26y09EuKzz/6PQCfV2Bl GGDMtUNG5YbntTZYYUbLzis= =NPRz -----END PGP SIGNATURE----- --=-AaS2rjrjAGHXgSX5Oinl--