Gentoo Archives: gentoo-dev

From: "Tomáš Chvátal" <scarabeus@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] How do we handle stabilisations of not-exactly-maintained packages
Date: Tue, 20 Sep 2011 21:44:12
In Reply to: Re: [gentoo-dev] [RFC] How do we handle stabilisations of not-exactly-maintained packages by "Tony \\\"Chainsaw\\\" Vroon"
2011/9/20 Tony "Chainsaw" Vroon <chainsaw@g.o>:
> On Tue, 2011-09-20 at 23:18 +0200, Tomáš Chvátal wrote: >> Well it would be something like priority based queue with maximum 60 >> points value. >> Each update after the month in main tree would get 0 points for >> stabilisation, any-developer / maintainer would be able to add up to >> 40 points to any package and security team members would be able to >> add all 60 points. Security team/any developer would also have >> possibility to add new packages to queue manualy. > > This sounds to me like you are trying to automate common sense. If you > see packages that have good ~arch ebuilds that appear to be fermenting, > please file a bug. Rumours of unresponsive arch teams have been greatly > exaggerated! > > The worst that could happen is that a more exotic arch sees your bug and > decides "sorry, we would rather unkeyword it" rather than "okay, we will > stable that". Either way seems a valid outcome though? > > I can't speak for other arches than AMD64, but we are happy to receive > more than the current influx of bugs, particularly if you are willing to > take suggestions to heart (a lot of QA niggles get shaken out in AT > reports lately). > > Regards, > Tony V. >
I am not saying that Archs are unresponsive (well they are on ppc for example sometimes) but I try to solve other problem about finding what packages CAN go stable and nobody ever bothered to do a bugreport. Yeah we can do it by hand like robot and open bugs for zilions of packages just to get all the spell packages stable etc etc, but look on the euscan, it is quite usefull to have automatically generated report of what can you bump and what did you miss to update. Instead of waiting on maintainer/anyone to notice that you can stable something this would give you nice report itself. And usually when i update and qa clean some package in 30 days I don't even really remember which one it was :) Tom