Re: Bits from the Release Team - Kicking off Wheezy
On Sat, Apr 30, 2011 at 11:24:41PM -0700, Ludovico Cavedon wrote:
> On 04/30/2011 04:32 PM, Pierre Habouzit wrote:
> > FWIW I think that "rolling" or "CUT" miss the point entirely. As a
> > Debian user I use stable on my servers (with a few backports for the 3-4
> > things I need bleeding edge for). For my desktop I use unstable, and
> > when that breaks (which is *very* rare, really) I go to snapshots and go
> > back a few versions. I couldn't care about testing any less. And at
> > work, every person I know either uses just stable or does the same as
> > me. I know no testing user around me. Of course I'm not pretending I
> > know the absolute Truth, but well, I find this whole "users want testing
> > badly" thing dubious.
> I do know people who run testing.
> Actually I can see two kinds of users who run testing.
> -people who want to keep getting software updates, but do not want to
> run unstable . They would point to "testing" in their apt
> sources.list. These are the users who want "rolling"
> -people who would decided to run the next stable release, before it is
> actually released, they would point their sources.list to "wheezy" (as
> of now). there are the users who will go though "rolling", then
> "frozen", then "stable"
>  I run unstable in my laptop, and it is stable enough for me, but for
> a regular user I can see how these 10 days between unstable and testing
> can help her to avoid getting in contact with major bugs/issues.
I used to run testing in the sarge days. It was utterly broken with lots
of uninstallable (or hard to insall) stuff when you had KDE migrations
for example. I knew lots of people using testing at the time, we all
moved to unstable because it was just too hard trying to get to install
stuff at some point.
Plus, you also have the very real effect of "This RC bug that affects
testing isn't fixed for 50 days because the fix that sits in unstable
for now 45 cannot migrate because it's tangled in this or this
Okay I understand that rolling probably intends to fix the latter, but
I'm not sure it's that easily fixable without some kind of
testing-proposed-updates thing (which is a no-go because it means
testing receives non-unstable-tested packages), *or* is pretty much
impossible to achieve because you just can't make transition go faster,
but for NMUing the blockers.
·O· Pierre Habouzit