On Thu, 2006-07-27 at 09:24 -0600, Steve Dibb wrote:
> Chris Gianelloni wrote:
> >> I'd say no bugs, 30 days, passes internal tests, being run by users =>
> >> stablise, for the majority of packages (obviously, there may be some
> >> exceptions...).
> >>     
> >
> > Luckily, you're not making the call.  ;]
> >
> > The "majority" of packages are also the ones that need more extensive
> > testing.  Sure, we could probably stabilize a bunch of the fringe
> > packages that hardly anyone uses and it wouldn't affect anything.
> 
> That's actually how I read the first email, was that it's really the 
> majority of the _minor_ packages that get completely neglected, and just 
> sits in the tree for months or years marked unstable because nobody 
> cares.  The people that use it have marked it ~arch a long time ago in 
> their package.keywords because they know it works just fine.

Well, we would hope that people using the package would file a bug, but
this obviously doesn't always happen.

> THAT stuff I wouldn't mind going through and just bumping to stable 
> myself.  They don't need extensive testing, they don't need patches, 
> they work, and have been working, and just need arches flagged and 
> versions bumped.

I'd have no problem with that so long as it was done by a person.  I
just don't trust that anything like this should ever be automated.

Now, we could have an automated system to send out *alerts* on packages
that have been in testing for more than 30 (or 60) days.  We could even
make it searchable by architecture and put it on a web page.  We could
probably also make it give some information about QA problems.  We could
even make it searchable by herd.  That would be cool.

I propose that we put up such a page and we call it
http://gentoo.tamperd.net/stable/ and make it publicly available.  ;]

> But, nobody likes doing the small stuff, and I can't blame them.

True that.

-- 
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to