Hi, "- Release candidate votes can be carry over to the next RC by a release manager if they so desire"
I would suggest that we add something like: "and if it's uncontroversial to do so." Where uncontroversial means: no one objects. Otherwise a release manager could conceivably get the votes he needs for one RC, then cut another one with undesirable changes in it and release with the votes from the first one... EdB On Wed, Nov 6, 2013 at 4:38 AM, Mark Kessler <kesslerconsult...@gmail.com> wrote: > Looks reasonable. It's nice to have it all down in one place as well. > > -Mark > > > On Tue, Nov 5, 2013 at 10:28 PM, Justin Mclean > <jus...@classsoftware.com>wrote: > >> Hi, >> >> Despite Alex's efforts this seem to have stalled: >> >> http://mail-archives.apache.org/mod_mbox/incubator-general/201310.mbox/%3cce743d6a.14a96%25aha...@adobe.com%3e >> >> With a few voting issues coming up recently I think it time to consider >> having our own guidelines. >> >> Here some I put together from other Apache projects in combination how we >> have been working as a project: >> https://cwiki.apache.org/confluence/display/FLEX/Draft+Guidelines >> >> Recent changes include: >> - removed any mention of what defines an "active" committer or PMC member >> as it's controversial and can be easily gamed >> - put in some expected (but not required) committer responsibilities >> - filled in what are the default the voting rules >> >> There are some difference from the "default" Apache guidelines >> - Committers can veto checkins (seems a better match to me - not that >> there have been many veto's) >> - Release candidate votes can be carry over to the next RC by a release >> manager if they so desire >> - I also put the length of the Chair as a year with the option of them to >> stand for another year as that to me seem the fairest way to share that >> responsibility. >> >> Feedback is welcome. >> >> Thanks, >> Justin -- Ix Multimedia Software Jan Luykenstraat 27 3521 VB Utrecht T. 06-51952295 I. www.ixsoftware.nl
