NSW == some random phone substitution. I meant "specifics" On 14 May 2013 23:09, "Steve Loughran" <[email protected]> wrote:
> That's because i thought this was a PMC vote. I marked mine as non binding > as I'm only a commiter. Now that the NSW of this badly structured vote is > clearer, I would vote -1 binding on it unless it was clarified better and > accounted with a policy to receive how you would get forward API > compatibility while keeping out those features that you seem personally > opposed to.. > On 14 May 2013 21:42, "Konstantin Shvachko" <[email protected]> wrote: > >> Vinod, >> >> Steve explicitly marked his vote as non-binding. >> I counted it as such. >> >> Thanks, >> --Konst >> >> >> On Tue, May 14, 2013 at 1:15 PM, Vinod Kumar Vavilapalli < >> [email protected]> wrote: >> >> > >> > The vote count is wrong: >> > >> > 6 binding +1s >> > 5 binding -1s >> > 4 non-binding +1s >> > 2 non-binding -1s. >> > >> > I think you mis-counted stevel, whose vote is binding. >> > >> > On May 14, 2013, at 10:07 AM, Konstantin Shvachko wrote: >> > >> > > This vote passes with >> > > 6 binding +1s >> > > 4 non-binding +1 >> > > 4 binding -1 >> > > 3 non-binding -1 >> > > >> > > Thank you for voting, >> > > --Konstantin >> > > >> > > >> > > On Wed, May 1, 2013 at 12:53 PM, Konstantin Shvachko >> > > <[email protected]>wrote: >> > > >> > >> Please vote on the following plan for Hadoop release 2.0.5 >> > >> - bug fixes encountered in current release 2.0.4-alpha >> > >> - make all API changes to allow freezing them post 2.0.5 >> > >> - no new features >> > >> >> > >> As discussed on @dev thread >> > >> http://s.apache.org/fs >> > >> this will allow to stabilize 2.0 branch in a short and predictable >> > period >> > >> of time. >> > >> This enables a powerful option to have the release tested at Yahoo >> > scale. >> > >> The plan is to follow up with 2.1.0 - the stable release. >> > >> New features can and should be added on top of the stable release >> once >> > it >> > >> is out. >> > >> >> > >> Hadoop by-laws: >> > >> http://hadoop.apache.org/bylaws.html >> > >> >> > >> "Release Plan >> > >> Defines the timetable and actions for a release. The plan also >> > nominates a >> > >> Release Manager. >> > >> Lazy majority of active committers" >> > >> >> > >> assume nomination of a Release Manager with the plan. >> > >> It would be really good if Arun continues if this plan is adopted. >> > >> We can return to the RM topic if not. >> > >> >> > >> The vote will run for 7 days until next Wed, May 8th. >> > >> >> > >> Thanks, >> > >> --Konstantin >> > >> >> > >> > >> >
