As a mentor I've (nearly) always advised that if there are three IPMC votes on the dev list then there is no need to make further noise on the general list with unnecessary +1's. I therefore point out in the general@ vote mail that 3 binding (IPMC) +1's have been received and therefore there is only a need to vote if there is an objection.
I'm sure that some folks might claim the more correct process is to have a second vote, but as long as the 3 IPMC votes are formally and publicly recorded in the dev list vote then I believe that is all we need. TECHNICALITY: PPMC votes are not binding (although they absolutely should be considered as such by the project). Only IPMC votes are considered binding at the foundational level since PPMC members are not yet a member of a formal committee. Note I'm not suggesting that a PPMC vote is unimportant. In fact it is more important than IPMC votes at the project level, it's just the way we are structured means PPMC votes are not binding according to our bylaws (at least that's how I understand it). Sent from Surface From: Justin Mclean Sent: Thursday, July 24, 2014 3:57 PM To: general@incubator.apache.org Hi, Anyone clarify this as it's not mentioned at [1]. Whose votes are binding for releases on the podlings dev list? Obviously mentors and PPMC members, but are IPMC members votes binding? I would assume so but don't see it stated anywhere. Would Apache members votes be binding? Assuming IPMC votes are binding what happen if a podling release dev list vote got 3 +1 IPMC votes, would a voted need to done on general @ incubator or not? Thanks, Justin 1.http://incubator.apache.org/incubation/Incubation_Policy.html#Releases --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
