Re: [gentoo-dev] Change or revert the "30 days maintainer timeout" stabilization policy

[William Hubbs]

On Thu, Apr 03, 2014 at 04:30:20PM +0400, Mikle Kolyada wrote:
>
> 02.04.2014 20:52, Samuli Suominen пишет:
> > The "30 days maintainer time out" stabilization policy isn't working
> > when package has multiple SLOTs, because
> > the bugs are filed for only latest SLOT, where as some packages require
> > stabilization in sync at both SLOTs
> >
> > Option 1:
> >
> > Either revert the whole policy, and never CC arches on unanswered bugs
> > when the package has a maintainer,
> > and let him do it when he finds the time himself, and if that doesn't
> > happen, wait until it's dropped to maintainer-needed@
> >
> > Option 2:
> >
> > Or, the person who is CCing the arches in 30 days timeout, needs to make
> > sure the bug covers all SLOT at the same time
> >
> >
> > The status quo no longer allows me to maintain stable version of
> > dev-libs/girara, app-text/zathura*, and the issue needs
> > to be addressed, see http://bugs.gentoo.org/502714 for what inspired
> > this mail
> >
> > - Samuli
> Agreed. If package have active maintainer(s), i think they can file
> stablereq when they wants (i think all maintainers have stabilization
> scheme at least). As arch teams developer i'm annoyed when i see 80 (or
> even more) messages like *maintainer timeout, go ahead* Moreover last
> time i'm noticed, that this script CC s390/sh/m68k automatically, and we
> need remove it manually. Seems script stil has no fix at all.

I am for the automatic stabilization requests continuing.

It is easy for a maintainer who runs full ~arch or who is very active in
several projects to not file stabilization requests in a timely manor,
and this hurts our stable users.

As said before, if you don't want the maintainer timeout script to add
the arch's to a stable request, all you have to do is add a comment to
it.

William