Re: [gentoo-dev] aging ebuilds with unstable keywords

[Roman Gaufman <hackeron@gmail.com>]

Would make a very nice QA measure. Any outdated/broken ebuild could be
auto reported to bugzilla and removed in 72 hours if no responce.

I think gentoo really needs QA measures of this sort. Like in debian,
packages get moved up from unstable to testing automatically if no
critical reports were made for 2 weeks.

This could have really great potential. Tests can be added to the
script to track new discovered problems, then repoman can be tied down
on the same system as this periodic test.

Very nice idea indeed. Any chance we could see the code?

On Sun, 31 Oct 2004 10:25:25 +0100, Henrik Brix Andersen
<brix@gentoo.org> wrote:
> Hi,
> 
> On Sat, 2004-10-30 at 16:53, Daniel Ahlberg wrote:
> > This is an automatically created email message.
> > http://gentoo.tamperd.net/stable has just been updated with 8758 ebuilds.
> 
> Could someone please explain to me what the above mentioned site can be
> used for?
> 
> I've checked the site a few times, but my email isn't even listed in the
> drop-down list, and the package entries for packages maintained by the
> mobile herd (to which I am enslaved) are not exactly up-to-date.
> 
> Sincerely,
> Brix
> --
> Henrik Brix Andersen <brix@gentoo.org>
> Gentoo Linux
> 
> 
>

--
gentoo-dev@gentoo.org mailing list