what has been with the rule that an ipmc must forward the VOTE to the incubator pmc when it gets started, and those members can also cast a binding -1 ?
LieGrue, strub On Tuesday, 18 March 2014, 4:10, David Nalley <da...@gnsa.us> wrote: On Mon, Mar 17, 2014 at 1:10 PM, John D. Ament <john.d.am...@gmail.com> wrote: >> Hi all, >> >> While not specifically incubator related, was wondering if someone at >> the incubator may provide me some insight. >> >> Right now, release votes cannot be veto'd. This seems like an >> oversight IMHO. If a release candidate is visibly wrong (e.g. bad >> licenses, or something else), surely the release candidate can be >> veto'd no? >> > >This is correct - release votes are not veto-able. >In my opinion if you have a PMC whose members choose to ignore an >obviously problematic release, especially from a licensing standpoint, >then you have much bigger problems with the project. In my experience >two factors come into play: >1. The release manager, even with a vote that technically passes, will >not proceed with a vote where there are obvious major problems, >especially from a legal perspective. They cancel the vote on their own >accord. No one wants a majorly flawed release shipping. >2. Other PMC members heap on -1 votes if it remains open for any >length of time, effectively causing the vote to fail to pass. > >If you can't get agreement on the obviously wrong candidate, perhaps >it's not as obvious why its wrong. > >--David > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >For additional commands, e-mail: general-h...@incubator.apache.org > > > >
