Re: [gentoo-dev] GLEP 19, reloaded (again)

[Chris Gianelloni]

On Tue, 2004-08-10 at 09:24, Kurt Lieber wrote:
> The release schedule for liveCDs/package sets is 4/year.  We're talking
> about an annual cycle here.

At no point have I ever seen a cycle mentioned for the "stable" tree,
until now.  Also, I've stated in many threads before that -releng is
more than willing to work with whomever to make changes to the release
cycle to best serve the needs of our users.  UNFORTUNATELY, it seems
that people don't read most of the threads that go on here, so I have to
repeat myself quite a bit to get this out to everyone interested... ;]

> > 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 recommend
> > 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.
>
> No -- we would have one tree for each release, but the difference is that
> you're talking about using the tree to control versions and I'm talking
> about using profiles to control versions.  With the current proposal, the
> *only* difference between the main rsync module and the "stable" module is
> that the latter has the --delete option removed.  This is to ensure ebuilds
> remain in the tree for a predictable period of time.  It has nothing to do
> with package versioning.

So we move no closer to our goal of providing a stable/frozen
installation environment than to ensure ebuilds don't disappear from the
tree?  How is this really beneficial to our users?  Is there a reason
for completely separating the idea of a "stable" tree from our already
established releases?  Is there a reason why they cannot both be
modified to work together and do what is best for our users, gives them
the most choice, and gives them what they're actually asking for?

-- 
Chris Gianelloni
Release Engineering QA Manager/Games Developer
Gentoo Linux

Is your power animal a penguin?