1 |
On Mon, 21 Oct 2013 13:44:57 -0400 |
2 |
Rich Freeman <rich0@g.o> wrote: |
3 |
|
4 |
If you read that as: |
5 |
|
6 |
> "If a maintainer has [...] a KEYWORDREQ blocking a |
7 |
> pending STABLEREQ, for 90 days with archs CCed and otherwise ready |
8 |
> to be stabilized [...] |
9 |
|
10 |
where you would sensibly assume that any KEYWORDREQ that is -not- |
11 |
needed for a STABLEREQ is flawed, then all this is superfluous: |
12 |
|
13 |
> Are there any objections to changing "the maintainer can remove older |
14 |
> stable versions of the package at their discretion" to "the |
15 |
> maintainer can remove older versions of the package at their |
16 |
> discretion?" In the case of a KEYWORDREQ the older version might not |
17 |
> be stable. |
18 |
|
19 |
Keyword requests that do not block stabilisation requests should be |
20 |
requested by users of the specified architectures or should go |
21 |
to /dev/null. Keyword requests that do block stabilisation requests |
22 |
should get the same treatment as the stabilisation requests that they |
23 |
block. How else would you resolve them? |
24 |
|
25 |
> Surely if a stable version can be removed, an unstable one could be... |
26 |
|
27 |
Yes. |
28 |
|
29 |
|
30 |
jer |