| 1 |
On 11/17/2016 01:49 PM, Michael Orlitzky wrote: |
| 2 |
> On 11/17/2016 02:16 AM, Michael Palimaka wrote: |
| 3 |
>> |
| 4 |
... |
| 5 |
> |
| 6 |
>> === amd64 === |
| 7 |
>> * Any developer may perform {{keyword|amd64}} stabilisations - it is not |
| 8 |
>> necessary to be on the arch team |
| 9 |
>> |
| 10 |
>> === x86 === |
| 11 |
>> * Any developer may perform {{keyword|x86}} stabilisations - it is not |
| 12 |
>> necessary to be on the arch team |
| 13 |
> |
| 14 |
> The arch teams are OK with this now? If so I can go close some STABLEREQs... |
| 15 |
> |
| 16 |
> |
| 17 |
|
| 18 |
Strictly speaking GLEP 40 forbids it still, although some arch teams |
| 19 |
have made announcements to approve it, see e.g [1,2]. I wouldn't be |
| 20 |
surprised if one of the results of the stable WG is an updated GLEP 40 |
| 21 |
that (new GLEP replacing existing) that allows for MAINTAINER |
| 22 |
self-stabilization. Personally I don't like "any developer may perform" |
| 23 |
part of it. The maintainer is responsible, and should at least ack |
| 24 |
stabilization at all before anything is stabilized (for arch-team |
| 25 |
stabilization as well), and consequently individual stabilizations by |
| 26 |
developers, either the maintainer itself or someone with applicable |
| 27 |
hardware. |
| 28 |
|
| 29 |
References: |
| 30 |
[1] |
| 31 |
https://archives.gentoo.org/gentoo-dev/message/355f4b4272c0049cffcdec88d815e267 |
| 32 |
[2] |
| 33 |
https://archives.gentoo.org/gentoo-dev/message/1246dd8fabe44e7e7ecf59ecf029af3e |
| 34 |
|
| 35 |
-- |
| 36 |
Kristian Fiskerstrand |
| 37 |
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net |
| 38 |
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3 |
Archives