Re: [gentoo-dev] [RFC] Reworking package stabilization policies

[Maciej Mrozowski]

On Saturday 27 of March 2010 21:58:41 William Hubbs wrote:
> On Sat, Mar 27, 2010 at 05:45:51PM +0100, Torsten Veller wrote:
> > * Petteri R?ty <betelgeuse@g.o>:
> > > So let's summarize for assigning to the single arch:
> > >
> > > In support (and my comments in support):
> > >  - Can be used as a gentle reminder for slacker arches
> >
> > And if not "only one arch" or "single arch" is slacking?
> > I guess you would find another gentle way to remind them.
> >
> >
> > How about a tool generating mails to arch teams, which lists all
> > STABLEREQ, KEQWORDREQ bugs to which the arch team is CC'ed for a month?
> > (Or probably easier or possible at all: which weren't changed for 30
> > days.)
>
>  I know that I have several bugs right now with minor arch's on them
>  waiting to be stabilized.  A couple have been waiting for a very long
>  time.  I have even pinged some of the bugs several times with no response.
>
>  Is there anything else I can do to get these arch teams attention?

Yes, I think getting from them the privilege of being the only ones able to 
stabilize applications should do the job.

No, seriously - given the fact that some of my packages were even stabilized 
without contacting me (app-misc/hal-cups-utils, app-admin/system-config-
printer-common) - I think it should be:

* solely up to the package maintainers to stabilize application on arches 
they're using or on any arch if package is arch-agnostic (optionally, but 
preferably with some peer review from other project members or arch team 
members).

* to arch team members in other cases (like now)

* other rules (30 days 'waiting' period, bugzilla bug with STABLEREQ) applied 
as they are now

Role of arch teams would be decreased to peer review and solving KEYWORD 
requests.

It's really freaking silly to wait months for stabilization of some random 
php/perl library that's known to work.

Comments?

-- 
regards
MM