| 1 |
El mié, 02-04-2014 a las 14:22 -0400, Mike Gilbert escribió: |
| 2 |
> On Wed, Apr 2, 2014 at 12:52 PM, Samuli Suominen <ssuominen@g.o> wrote: |
| 3 |
> > The "30 days maintainer time out" stabilization policy isn't working |
| 4 |
> > when package has multiple SLOTs, because |
| 5 |
> > the bugs are filed for only latest SLOT, where as some packages require |
| 6 |
> > stabilization in sync at both SLOTs |
| 7 |
> > |
| 8 |
> > Option 1: |
| 9 |
> > |
| 10 |
> > Either revert the whole policy, and never CC arches on unanswered bugs |
| 11 |
> > when the package has a maintainer, |
| 12 |
> > and let him do it when he finds the time himself, and if that doesn't |
| 13 |
> > happen, wait until it's dropped to maintainer-needed@ |
| 14 |
> > |
| 15 |
> > Option 2: |
| 16 |
> > |
| 17 |
> > Or, the person who is CCing the arches in 30 days timeout, needs to make |
| 18 |
> > sure the bug covers all SLOT at the same time |
| 19 |
> > |
| 20 |
> > |
| 21 |
> > The status quo no longer allows me to maintain stable version of |
| 22 |
> > dev-libs/girara, app-text/zathura*, and the issue needs |
| 23 |
> > to be addressed, see http://bugs.gentoo.org/502714 for what inspired |
| 24 |
> > this mail |
| 25 |
> > |
| 26 |
> > - Samuli |
| 27 |
> > |
| 28 |
> |
| 29 |
> If you want to prevent packages from being "timed out", just leave a |
| 30 |
> comment on the bug saying so. If you don't even have time to do that |
| 31 |
> within a 30 day window, why are you the maintainer? |
| 32 |
> |
| 33 |
> Another option would be to add some kind of notation to metadata.xml. |
| 34 |
> |
| 35 |
|
| 36 |
The script CCing arches is at: |
| 37 |
http://git.overlays.gentoo.org/gitweb/?p=proj/arch-tools.git;a=blob;f=maintainer-timeout.py;h=ba8c322a4d7a834e274e0b7587c22f5d8ba8ce08;hb=HEAD |
| 38 |
|
| 39 |
Not sure if anyone has enough knowledge to improve it covering option |
| 40 |
two :/ (handling both slots) |
Archives