Joe, Yes, Joel's vote is not binding, but Chris (IPMC), Neha (PPMC) and mine (PPMC) are.
Thanks, Jun On Wed, Oct 3, 2012 at 8:29 AM, Joe Stein <crypt...@gmail.com> wrote: > Thanks Jun but for binding they have to be member of PPMC and IPMC and > those are not documented anywhere I could find, that was my question is if > Joel's vote is binding now... it would be upon graduating as would mine > but was not sure what the rules were now, more for my own edification than > anything else I am going to send email for IPMC to get a vote going there > > On Wed, Oct 3, 2012 at 11:26 AM, Jun Rao <jun...@gmail.com> wrote: > > > Joe, > > > > From https://incubator.apache.org/guides/releasemanagement.html#rules, > the > > rules are: > > > > Each release requires a positive vote binding on Apache. This means a . > > There is usually no need for this vote to be private. (A rare exception > > might be a -1 due to a nearly discovered security issue, for example.) > > > > In the case of podlings, a 3 binding +1s are required by members of > > the Incubator > > PMC< > > https://incubator.apache.org/guides/releasemanagement.html#glossary-ipmc > >. > > To increase the chances of a prompt approval, mentors need to cast their > > votes on the general list. > > > > So, in IPMC voting, we just need more +1 binding votes then -1s. > > > > Thanks, > > > > Jun > > > > On Wed, Oct 3, 2012 at 8:12 AM, Joe Stein <crypt...@gmail.com> wrote: > > > > > I am closing the vote, the vote passes at least three PPMC binding > votes > > > and I will send an vote request to the get two more IPMC votes (Chris > > being > > > a member of the IPMC, right?) > > > > > > I say at least three as I am not sure if Joel's vote is binding or not. > > > Let me know so I when I vote. > > > > > > On Wed, Oct 3, 2012 at 2:01 AM, Chris Douglas <cdoug...@apache.org> > > wrote: > > > > > > > +1 > > > > > > > > Checksum and signature match, LICENSE, et al. look good. -C > > > > > > > > On Fri, Sep 28, 2012 at 7:40 PM, Joe Stein <crypt...@gmail.com> > wrote: > > > > > Hello, > > > > > > > > > > This is the fifth candidate for the third incubator release for > > Apache > > > > > Kafka, version 0.7.2-incubating. > > > > > > > > > > This release fixes the following issues > > > > > > > > > > > > > > > http://people.apache.org/~joestein/kafka-0.7.2-incubating-candidate-5/RELEASE-NOTES.html > > > > > > > > > > *** Please download, test and vote by Monday October, 1st, 9pm PDT > > *** > > > > > > > > > > Release artifacts to be voted upon: > > > > > > > > > https://people.apache.org/~joestein/kafka-0.7.2-incubating-candidate-5/ > > > > > > > > > > The tag (off the 0.7.2 branch) for release artifacts: > > > > > > > > > > > > > > > https://svn.apache.org/repos/asf/incubator/kafka/tags/kafka-0.7.2-incubating-candidate-5 > > > > > > > > > > Kafka's KEYS file containing PGP keys we use to sign the release: > > > > > https://svn.apache.org/repos/asf/incubator/kafka/KEYS > > > > > > > > > > /* > > > > > Joe Stein > > > > > http://www.linkedin.com/in/charmalloc > > > > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > > > > */ > > > > > > > > > > > > > > > > -- > > > > > > /* > > > Joe Stein > > > http://www.linkedin.com/in/charmalloc > > > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > > > */ > > > > > > > > > -- > > /* > Joe Stein > http://www.linkedin.com/in/charmalloc > Twitter: @allthingshadoop <http://www.twitter.com/allthingshadoop> > */ >
