FESCo wants to ban direct stable pushes in Bodhi (urgent call for feedback)

[James Antill]

On Wed, 2010-03-03 at 01:54 +0100, Kevin Kofler wrote:
> James Antill wrote:
> >  Users don't get a constant firehose of updates they are basically
> > forced to install, a lot more packages should spend a lot more time in
> > testing (thus. the user can choose to get the updates or updates-testing
> > versions).
> >  How is that not more choice than "here's rawhide-12, you are now forced
> > to test it for me"?
> 
> Well, I see where you're getting to now, but this is really not what 
> updates-testing is for! Updates-testing is for TESTING updates, not for 
> being used as production by some users, even those who want more updates.

 It would be used as production by users like _you_, not normal users.

>  I 
> want many updates, but I don't want to be the guinea pig for updates which 
> just hit testing,

 And nobody else wants to be the guinea pig for _you_.

>  and I also don't want to have to selectively update 
> because it's a mess.

 Why's that? Maybe because of the sheer volume of updates ... because of
packagers like...

> (and in fact this subtle detail changes your 
> proposal from something I consider excess bureaucracy, but could live
> with to something entirely unacceptable).

 I'll take that as a compliment, thanks.

>  Do you want users of stable to suffer through KDE 
> bugs or be forced to use testing?

 Again with the "suffering users" because they don't get 6GB of updates
a month? I think not, and I'm not alone.

>  You're effectively forcing everybody to 
> use testing

 No, that's your proposal ... mine allows people who want to get lots of
packages to do so and those who have a working system to not be forced
to test your package of the week.
 Yes, that means that people who want insane amount of updates (like
you) will have to do more testing than the rest ... but this is fine,
nobody owes you months of testing.

> In my 
> list, a package which requires 7 DSUT total always requires 7 DSUT total 
> (i.e. it will sit at least a week in testing, usually at most 2 weeks),

 You keep saying that 7 days is "enough" but I haven't seen you provide
_any_ evidence to support it. Noting that it will often take 3-4 days
before a package in testing can be seen by all users. So maybe you are
under the impression that all the users who would test your package are
anxiously waiting for your packages to be available?
 More likely you just don't want any real testing done, because hey ...
that's what all the users in stable are for, right?

> whether it's the first, the second or the 10000000th update.

 While it wouldn't surprise me if you did 10 million updates for KDE,
and assumed that was a good idea, I would bet a lot that users wouldn't
think that was a good idea.

-- 
James Antill - james at fedoraproject.org
http://yum.baseurl.org/wiki/releases
http://yum.baseurl.org/wiki/whatsnew/3.2.27
http://yum.baseurl.org/wiki/YumMultipleMachineCaching