I was trying to type this in the original message, but failed to find the right wording, so I kept it out (my wording would've been confusing).
Thanks! Martijn On Sat, Aug 29, 2009 at 8:59 AM, Niclas Hedhman<[email protected]> wrote: > On Fri, Aug 28, 2009 at 11:08 PM, Martijn > Dashorst<[email protected]> wrote: > >> ***Releases may not be vetoed***. > > To be absolutely clear; Yes they sort of can. If someone points out a > *legal* problem, the release manager must not proceed. The release > manager can also (after all it is volunteer effort) halt the release > based on input from community, and community may have its own > unwritten policy that full consensus should be achieved... so, there > are variants... > > Veto on Commits is otherwise the tool to stop 'bad things', typically > things like "breaking compatibility" and "security issue" are > candidates for vetoes. Note, vetoes without justification are invalid, > and justifications like "I don't like it" or "we don't need this > feature" are no good as vetoes. > > > Cheers > -- > Niclas Hedhman, Software Developer > http://www.qi4j.org - New Energy for Java > > I live here; http://tinyurl.com/2qq9er > I work here; http://tinyurl.com/2ymelc > I relax here; http://tinyurl.com/2cgsug > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.0
