Gentoo Archives: gentoo-releng

From: Lance Albertson <ramereth@g.o>
To: gentoo-releng@l.g.o
Subject: Re: [gentoo-releng] 2004.2 planning
Date: Sun, 02 May 2004 17:04:15
Message-Id: 1083517448.981.3.camel@pursuit
In Reply to: Re: [gentoo-releng] 2004.2 planning by Donnie Berkholz
1 On Sun, 2004-05-02 at 11:45, Donnie Berkholz wrote:
2 > On Sun, 2004-05-02 at 09:32, Nathaniel McCallum wrote:
3 > > On Sun, 2004-05-02 at 07:29 -0400, Kurt Lieber wrote:
4 > > > * Releases are largely meaningless, comprised of nothing more than package
5 > > > updates for GRP.
6 > >
7 > > Lets use 2004.x quarterly releases to perfect our GRP proceedure and get
8 > > GRP online. Once we are at that point we can divorce GRP from liveCD
9 > > releases if we need to.
10 >
11 > Exactly what I was thinking when reading this thread. Just provide a
12 > package+stages CD (or two) quarterly, and let them use a LiveCD from the
13 > (biannual?) LiveCD release. From what I see, it appears that much of the
14 > QA time goes into getting the LiveCDs working properly.
15
16 Funny, I was actually just thinking of that last night before I went to
17 bed. I see that quarterly releases for stages/grp package sets are
18 needed, but I really don't see a need for quarterly livecd releases.
19 There needs to be enough time to work out bugs/implement new features,
20 etc. The only thing that I can see for quarterly releases is driver
21 upgrades on the kernels used on the livecds. So, that may be debatable.
22
23 Thoughts?
24
25 (mind you, any changes I suggest would start in the 2005.x release
26 schedule)
27
28 --
29 Lance Albertson <ramereth@g.o>
30 Gentoo Infrastructure
31
32 ---
33 GPG Public Key: <http://www.ramereth.net/lance.asc>
34 Key fingerprint: 0423 92F3 544A 1282 5AB1 4D07 416F A15D 27F4 B742
35
36 ramereth/irc.freenode.net

Attachments

File name MIME type
signature.asc application/pgp-signature

Replies

Subject Author
Re: [gentoo-releng] 2004.2 planning Nathaniel McCallum <npmccallum@g.o>
Re: [gentoo-releng] 2004.2 planning John Davis <zhen@g.o>