1 |
02.04.2014 20:52, Samuli Suominen пишет: |
2 |
> The "30 days maintainer time out" stabilization policy isn't working |
3 |
> when package has multiple SLOTs, because |
4 |
> the bugs are filed for only latest SLOT, where as some packages require |
5 |
> stabilization in sync at both SLOTs |
6 |
> |
7 |
> Option 1: |
8 |
> |
9 |
> Either revert the whole policy, and never CC arches on unanswered bugs |
10 |
> when the package has a maintainer, |
11 |
> and let him do it when he finds the time himself, and if that doesn't |
12 |
> happen, wait until it's dropped to maintainer-needed@ |
13 |
> |
14 |
> Option 2: |
15 |
> |
16 |
> Or, the person who is CCing the arches in 30 days timeout, needs to make |
17 |
> sure the bug covers all SLOT at the same time |
18 |
> |
19 |
> |
20 |
> The status quo no longer allows me to maintain stable version of |
21 |
> dev-libs/girara, app-text/zathura*, and the issue needs |
22 |
> to be addressed, see http://bugs.gentoo.org/502714 for what inspired |
23 |
> this mail |
24 |
> |
25 |
> - Samuli |
26 |
Agreed. If package have active maintainer(s), i think they can file |
27 |
stablereq when they wants (i think all maintainers have stabilization |
28 |
scheme at least). As arch teams developer i'm annoyed when i see 80 (or |
29 |
even more) messages like *maintainer timeout, go ahead* Moreover last |
30 |
time i'm noticed, that this script CC s390/sh/m68k automatically, and we |
31 |
need remove it manually. Seems script stil has no fix at all. |
32 |
|
33 |
-- |
34 |
Mikle Kolyada |
35 |
Gentoo Linux Developer |