Gentoo Archives: gentoo-dev

From: Mike Gilbert <floppym@g.o>
To: Gentoo Dev <gentoo-dev@l.g.o>
Subject: Re: [gentoo-dev] Change or revert the "30 days maintainer timeout" stabilization policy
Date: Wed, 02 Apr 2014 18:22:36
Message-Id: CAJ0EP40PA_YznyL3tVCYN7Ry0QqwR1h6PHB25nb2N8+x2moq1w@mail.gmail.com
In Reply to: [gentoo-dev] Change or revert the "30 days maintainer timeout" stabilization policy by Samuli Suominen
1 On Wed, Apr 2, 2014 at 12:52 PM, Samuli Suominen <ssuominen@g.o> wrote:
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 >
27
28 If you want to prevent packages from being "timed out", just leave a
29 comment on the bug saying so. If you don't even have time to do that
30 within a 30 day window, why are you the maintainer?
31
32 Another option would be to add some kind of notation to metadata.xml.

Replies