public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Petteri Räty" <betelgeuse@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Requiring two sets of eyes for all eclass commits
Date: Sun, 25 Apr 2010 16:10:10 +0300	[thread overview]
Message-ID: <4BD43F32.3090409@gentoo.org> (raw)
In-Reply-To: <201004261042.36116.ali_bush@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]

On 04/26/2010 01:42 AM, Alistair Bush wrote:
>> On 04/24/2010 09:14 PM, Alexis Ballier wrote:
>>> On Sat, 24 Apr 2010 20:40:54 +0300
>>>
>>> Petteri Räty <betelgeuse@gentoo.org> wrote:
>>>> 17:34 < Betelgeuse> robbat2|na: how easy to it to prevent commits to
>>>> CVS if the commit message doesn't match a certain pattern?
>>>> 17:36 <@robbat2|na> go and checkout the CVSROOT and there should be an
>>>> example there
>>>> 17:37 < Betelgeuse> robbat2|na: Ok so doable then. Thanks.
>>>>
>>>> What do you think about not allowing commits to eclasses without
>>>> mentioning an another developer who has reviewed and approved the diff
>>>> in the commit message? There's enough people on gentoo-dev for urgent
>>>> stuff too.
>>>
>>> no thanks; we already have the policy to require that major changes to
>>> broad impact eclasses have gone through -dev, no need to add more
>>> bureaucracy.
>>
>> But the policy is not tested by the quizzes and we have had cases lately
>> where large diffs have been committed without gentoo-dev review. With
>> peer review it's likely that the reviewer is familiar with what should
>> be sent to gentoo-dev as hesitant/new people won't give their approval
>> that easily.
> 
> 1)  Why is it of any relevance whether or not the quizzes test this policy?  

I doubt recruits read all of our documentation while answering the
quizzes. This would just enforce behavior.

> 2)  Where is this policy recorded, and why does devmanual.g.o seem to 
> (possibly) contradict it? [1]  I'm not sure of the nature of the commits but 
> were they non-general?
> 

http://devmanual.gentoo.org/eclass-writing/index.html

"Before updating eutils  or a similar widely used eclass, it is best to
email the gentoo-dev list."

> 
> [1] "It is not usually necessary to email the gentoo-dev list before making 
> changes to a non-general eclass which you maintain. Use common sense here."

Yeah it's not spelled that clearly there.

Regards,
Petteri


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 900 bytes --]

  reply	other threads:[~2010-04-25 13:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-24 17:40 [gentoo-dev] Requiring two sets of eyes for all eclass commits Petteri Räty
2010-04-24 18:10 ` Arun Raghavan
2010-04-24 18:14 ` Alexis Ballier
2010-04-25 10:14   ` Petteri Räty
2010-04-25 22:42     ` Alistair Bush
2010-04-25 13:10       ` Petteri Räty [this message]
2010-04-25 15:22         ` Jorge Manuel B. S. Vicetto
2010-04-26 17:58       ` Steev Klimaszewski
2010-04-25 10:06 ` [gentoo-dev] " Ryan Hill
2010-04-25 10:11   ` Petteri Räty
2010-04-25 11:36     ` Ryan Hill
2010-04-25 12:01       ` Alec Warner
2010-04-25 21:06         ` Ryan Hill
2010-04-25 12:04       ` Richard Freeman
2010-04-26 16:19     ` Paul Varner
2010-04-25 10:54 ` [gentoo-dev] " Roy Bamford
2010-04-27 19:11 ` Rémi Cardona

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=4BD43F32.3090409@gentoo.org \
    --to=betelgeuse@gentoo.org \
    --cc=gentoo-dev@lists.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