From: Kristian Fiskerstrand <k_f@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Rich Freeman <rich0@gentoo.org>
Subject: Re: [gentoo-dev] taking a break from arches stabilization
Date: Mon, 10 Jul 2017 22:17:34 +0200 [thread overview]
Message-ID: <e2c8a847-f5e9-1c63-a8f5-57d890903432@gentoo.org> (raw)
In-Reply-To: <CAGfcS_krTJ9GAbW7S4P4XsDiLgd9EMW98CENXPT=LBrq4jCMKg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1755 bytes --]
On 07/10/2017 10:02 PM, Rich Freeman wrote:
> On Mon, Jul 10, 2017 at 3:57 PM, Andrew Savchenko <bircoph@gentoo.org> wrote:
>>
>> On Mon, 10 Jul 2017 13:49:40 -0400 Rich Freeman wrote:
>>
>>> In the case of amd64 we already
>>> encourage individual package maintainers to stabilize their own
>>> packages
>>
>> Huh? Have our rules changed? As per devmanual[1] and GLEP 40[2]
>> stabilization must be carried out by arch teams, unless a special
>> arrangement is done between a developer and a team.
>>
>
> The docs are probably out of date - I'm not sure if the policy is
> documented anywhere. However it has been a fairly longstanding policy
> at this point that amd64 allows individual maintainers to stabilize
> their own packages.
>
We looked after it for wg-stable (which died out as a result of rather
low participation, maybe it should be rebooted if people feel like
discussing this again), there isn't any authoritative policy allowing
it, GLEP:40 explicitly removes the possibility to do it for x86. That
said, for a number of packages maintainer stabilization can likely make
sense, the opposite view is four-eyes principle, it is always good to
have someone else build-test etc, but this is greatly helped by
tinderboxing efforts (thanks toralf) etc. So one likely output if
wg-stable is to come up with something would be a replacement GLEP for
40 that matches the current state, and also kernel auto-stabiliation (as
discussed in [section 3.2 (Kernel)]
References:
[section 3.2 (Kernel)]
https://download.sumptuouscapital.com/gentoo/wg-stable/main.pdf
--
Kristian Fiskerstrand
OpenPGP keyblock reachable at hkp://pool.sks-keyservers.net
fpr:94CB AFDD 3034 5109 5618 35AA 0B7F 8B60 E3ED FAE3
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2017-07-10 20:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 17:22 [gentoo-dev] taking a break from arches stabilization Agostino Sarubbo
2017-07-10 17:35 ` Alexis Ballier
2017-07-10 17:49 ` Rich Freeman
2017-07-10 19:57 ` Andrew Savchenko
2017-07-10 20:02 ` Rich Freeman
2017-07-10 20:17 ` Kristian Fiskerstrand [this message]
2017-07-10 23:29 ` Andrew Savchenko
2017-07-11 12:59 ` [gentoo-dev] " Michael Palimaka
2017-07-11 13:06 ` Rich Freeman
2017-07-11 13:47 ` Michael Palimaka
2017-07-11 14:13 ` Kristian Fiskerstrand
2017-07-11 14:15 ` Kristian Fiskerstrand
2017-07-11 14:21 ` Michael Palimaka
2017-07-11 21:26 ` Kristian Fiskerstrand
2017-07-11 22:13 ` Thomas Deutschmann
2017-07-11 22:27 ` Kristian Fiskerstrand
2017-07-12 13:19 ` Marek Szuba
2017-07-11 23:12 ` Mart Raudsepp
2017-07-12 11:59 ` Michael Palimaka
2017-07-12 12:30 ` Kristian Fiskerstrand
2017-07-12 14:13 ` William Hubbs
2017-07-12 14:35 ` Pacho Ramos
2017-07-11 14:25 ` James Le Cuirot
2017-07-11 14:35 ` Michael Palimaka
2017-07-11 14:43 ` Rich Freeman
2017-07-11 14:16 ` Michael Palimaka
2017-07-11 17:16 ` William Hubbs
2017-07-12 0:03 ` Sam Jorna (wraeth)
2017-07-10 18:11 ` [gentoo-dev] " Jonas Stein
2017-07-10 18:42 ` Mike Pagano
2017-07-10 19:09 ` Matt Turner
2017-07-10 19:53 ` Rich Freeman
2017-07-10 20:05 ` M. J. Everitt
2017-07-10 20:27 ` Rich Freeman
2017-07-10 23:54 ` Andrew Savchenko
2017-07-11 12:58 ` Rich Freeman
2017-07-11 0:48 ` Aaron Bauman
2017-07-11 8:32 ` Lars Wendler
2017-07-11 11:56 ` Agostino Sarubbo
2017-07-11 19:31 ` Daniel Campbell
2017-07-12 14:21 ` Sergey Popov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e2c8a847-f5e9-1c63-a8f5-57d890903432@gentoo.org \
--to=k_f@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=rich0@gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox