Hmmm, I still did not see answers to my questions around the timelines for the
Hadoop API stabilization which will influence my vote on this topic.
Apart from that voting for a release that is not yet planned is not defined in
the bylaws. I think its closer to the "Release Plan" than it is to "Product
Release" action. Irrespective, both of them require Lazy Majority
<snip>
Release Plan Defines the timetable and actions for a release. The plan also
nominates a Release Manager. Lazy majority Active committers 3
Product Release When a release of one of the project's products is ready, a
vote is required to accept the release as an official release of the project.
Lazy Majority Active PMC members 3
</snip>
-----Original Message-----
From: Olga Natkovich [mailto:[email protected]]
Sent: Monday, March 07, 2011 3:21 PM
To: [email protected]
Subject: [VOTE] Pig 1.0!
Hi guys,
We had a lively discussion last week regarding what version number to assign to
the major release following Pig 0.9. The discussion can be seen here:
http://tinyurl.com/4ng8upa.
Based on the discussion, it seemed that most people were on-board with making
next release Pig 1.0 as long as we have done good job stabilizing post Pig 0.9.
I would like to call vote on calling the release Pig 1.0. I believe it is
important to finalize the version number prior to starting the work on the
release. I believe that this vote is part of Product Release Action and as such
is subject to Lazy Majority vote: http://pig.apache.org/bylaws.html.
Please, complete the vote by the end of this Thursday, 3/10. Please, note that
anybody is welcome to vote but only PMC votes are binding.
Olga
