public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP
Date: Sat, 22 Jun 2013 11:46:02 +0200	[thread overview]
Message-ID: <20933.29274.438907.585923@a1i15.kph.uni-mainz.de> (raw)
In-Reply-To: <20933.26517.731140.317442@a1i15.kph.uni-mainz.de>

>>>>> I wrote:

>>>>> On Sat, 22 Jun 2013, Robin H Johnson wrote:
>> So we have:
>> Who = {ANYTHING_GOES, REQUIRES_DEV, REQUIRES_HERD, REQUIRES_MAINTAINER}
>> What = {NONE, TRIVIAL, MINOR_FEATURES, VERSION_BUMP, MAJOR_FEATURES}

>> So most of my packages might be coded with:
>> <nmu-policy who="REQUIRES_DEV" what="VERSION_BUMP" />
>> <nmu-policy who="REQUIRES_HERD" what="MAJOR_FEATURES" />

>> - If you're a developer, you can do trivial fixes, add minor features,
>>   bump the version.
>> - If you're in the herd, you can add major features.

> Shouldn't this be REQUIRES_TEAM instead? A "herd" used to be a
> collection of packages, whereas the devs maintaining them were
> called a team. Or don't we care about this distinction any more?

Getting back on topic: Apart from this minor issue, I think that your
proposal is quite reasonable.

Ulrich


  parent reply	other threads:[~2013-06-22  9:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-21 18:50 [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Robin H. Johnson
2013-06-21 19:04 ` Alexis Ballier
2013-06-21 19:07   ` Robin H. Johnson
2013-06-21 19:31     ` Alexis Ballier
2013-06-22  1:11   ` Tom Wijsman
2013-06-21 20:31 ` Michael Weber
2013-06-21 20:41   ` Michael Weber
2013-06-22  1:21     ` Tom Wijsman
2013-06-21 23:40 ` Mike Frysinger
2013-06-22  0:06   ` Robin H. Johnson
2013-06-22  0:17     ` Mike Frysinger
2013-06-22  0:26       ` Robin H. Johnson
2013-06-22  1:06         ` Mike Frysinger
2013-06-22  1:42           ` Robin H. Johnson
2013-06-22  3:28             ` Rick "Zero_Chaos" Farina
2013-06-22  9:00             ` Ulrich Mueller
2013-06-22  9:05               ` hasufell
2013-06-22  9:38                 ` [gentoo-dev] Herds (was: Soliciting input for a non-maintainer update (NMU) GLEP) Ulrich Mueller
2013-06-22  9:48                   ` [gentoo-dev] Herds hasufell
2013-06-22  9:46               ` Ulrich Mueller [this message]
2013-06-22 10:43               ` [gentoo-dev] Soliciting input for a non-maintainer update (NMU) GLEP Rich Freeman
2013-06-22  9:01             ` hasufell
2013-06-22 10:20               ` Michael Weber
2013-06-22 10:39                 ` Rich Freeman
2013-06-22 10:52                 ` Tom Wijsman
2013-06-22 17:59                 ` Mike Frysinger
2013-06-22  9:16             ` Markos Chandras
2013-06-22 10:19             ` Tom Wijsman
2013-06-22 13:42             ` [gentoo-dev] " Michael Palimaka
2013-06-22 15:13             ` [gentoo-dev] " hasufell
2013-06-22 16:56               ` Robin H. Johnson
2013-06-22 10:11     ` Pacho Ramos
2013-06-23  3:01       ` Rick "Zero_Chaos" Farina
2013-06-27 18:18         ` hasufell
2013-06-27 19:29           ` Rick "Zero_Chaos" Farina

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=20933.29274.438907.585923@a1i15.kph.uni-mainz.de \
    --to=ulm@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