1 |
On Fri, Jun 21, 2013 at 09:06:30PM -0400, Mike Frysinger wrote: |
2 |
> On Friday 21 June 2013 20:26:03 Robin H. Johnson wrote: |
3 |
> > On Fri, Jun 21, 2013 at 08:17:38PM -0400, Mike Frysinger wrote: |
4 |
> > > > I'm not going into review systems here at all, I'm simply trying to |
5 |
> > > > have a policy of what changes are welcomed/blocked WITHOUT interaction |
6 |
> > > > from the listed maintainer(s) of a given package/herd. |
7 |
> > > |
8 |
> > > add a new field to metadata.xml that declares the state. make it an enum: |
9 |
> > > ANYTHING_GOES (the default) |
10 |
> > > REQUIRES_HERD |
11 |
> > > REQUIRES_MAINTAINER |
12 |
> > |
13 |
> > I wish it was that easy. |
14 |
> > |
15 |
> > Despite being ANYTHING_GOES on most of my packages, I don't want people |
16 |
> > to add giant features like qmail patchbombs; so we need to figure out |
17 |
> > something like the Debian NMU listing of what's acceptable. |
18 |
> the maintainers intent has to be machine codable |
19 |
So we have the following facets of NMU permissions: |
20 |
Who |
21 |
What |
22 |
|
23 |
> > Does a version bump count as an acceptable trivial change? |
24 |
> that's up to the maintainer |
25 |
This needs to be in the above data: |
26 |
|
27 |
So we have: |
28 |
Who = {ANYTHING_GOES, REQUIRES_DEV, REQUIRES_HERD, REQUIRES_MAINTAINER} |
29 |
What = {NONE, TRIVIAL, MINOR_FEATURES, VERSION_BUMP, MAJOR_FEATURES} |
30 |
|
31 |
So most of my packages might be coded with: |
32 |
<nmu-policy who="REQUIRES_DEV" what="VERSION_BUMP" /> |
33 |
<nmu-policy who="REQUIRES_HERD" what="MAJOR_FEATURES" /> |
34 |
|
35 |
- If you're a developer, you can do trivial fixes, add minor features, |
36 |
bump the version. |
37 |
- If you're in the herd, you can add major features. |
38 |
|
39 |
-- |
40 |
Robin Hugh Johnson |
41 |
Gentoo Linux: Developer, Trustee & Infrastructure Lead |
42 |
E-Mail : robbat2@g.o |
43 |
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85 |