On Friday 21 June 2013 20:26:03 Robin H. Johnson wrote: > On Fri, Jun 21, 2013 at 08:17:38PM -0400, Mike Frysinger wrote: > > > I'm not going into review systems here at all, I'm simply trying to > > > have a policy of what changes are welcomed/blocked WITHOUT interaction > > > from the listed maintainer(s) of a given package/herd. > > > > add a new field to metadata.xml that declares the state. make it an enum: > > ANYTHING_GOES (the default) > > REQUIRES_HERD > > REQUIRES_MAINTAINER > > I wish it was that easy. > > Despite being ANYTHING_GOES on most of my packages, I don't want people > to add giant features like qmail patchbombs; so we need to figure out > something like the Debian NMU listing of what's acceptable.
the maintainers intent has to be machine codable > Does this need to be coded in the metadata? yes. we already have maintainer info in there, and putting it anywhere else is doomed to failure. > Does a version bump count as an acceptable trivial change? that's up to the maintainer -mike
signature.asc
Description: This is a digitally signed message part.
