1 |
hasufell posted on Sun, 10 Mar 2013 19:11:52 +0100 as excerpted: |
2 |
|
3 |
> I was told a while back (I might still have it in irc logs), that 30 |
4 |
> days is NOT a rule. It's common sense, but in the end the maintainer |
5 |
> decides when to request stabilization, no one else. |
6 |
|
7 |
I can confirm the 30-day-guideline policy was just that, a maintainer- |
8 |
discretion guideline, back in 2005/2006 or so when I first became aware |
9 |
of the concept via discussion. It was explained as maintainer knows |
10 |
their packages best, with the caveat that arch-teams also knew their archs |
11 |
best and could choose not to stabilize right away if they decided the |
12 |
request wasn't appropriate for their arch. |
13 |
|
14 |
I've seen no council, etc. decision changing that, over the years. |
15 |
|
16 |
Sometime a bit thereafter, various understaffed archs began to yield |
17 |
stabilizing authority to non-arch-team maintainers on a package-by- |
18 |
package basis, generally with at least the requirement that said |
19 |
maintainer actually had access to and had tested on that arch. AFAIK, |
20 |
before that maintainers weren't to stabilize at all on archs they weren't |
21 |
team members of, but they could still do so if they were a member of the |
22 |
arch-team, provided of course that they were following arch-team policy |
23 |
in the process. |
24 |
|
25 |
Meanwhile, jer's explanation, that on an arch where the package was not |
26 |
previously stable, there could be no stable users of the app to see |
27 |
regressions, so straight to stable makes a bit more sense, makes perfect |
28 |
sense to me. =:^) |
29 |
|
30 |
If I'm arguably too verbose, vapier's arguably not verbose enough. Had |
31 |
he just said something like either of these instead of simply punting |
32 |
with his replies... I guess it would have stopped there. |
33 |
|
34 |
-- |
35 |
Duncan - List replies preferred. No HTML msgs. |
36 |
"Every nonfree program has a lord, a master -- |
37 |
and if you use the program, he is your master." Richard Stallman |