Oh. And it would be good to have an explanation for -1 votes. Only one negative vote came with a reason so far.
Thanks, --Konstantin On Thu, May 9, 2013 at 7:58 AM, Suresh Srinivas <[email protected]>wrote: > I agree it was premature to start this vote and I also thought it was going > to be restarted given > the discussions Nicholas, Roman and Steve had started on this thread. > > I am -1 (binding) on this. > > > On Thu, May 9, 2013 at 6:12 AM, Arun C Murthy <[email protected]> wrote: > > > Konstantin, > > > > You know I've been strongly opposed to this due to the bad precedents it > > sets; as I've made clear publicly in the *-dev lists. > > > > I was under impression you would restart this vote, but my bad. > > > > I am going to -1 this (binding). > > > > Could you please consider my vote or should I start a new one to unroll > > this? > > > > thanks, > > Arun > > > > On May 8, 2013, at 10:40 PM, Konstantin Shvachko wrote: > > > > > My formal +1. > > > > > > Vote passes with > > > 3 binding +1s > > > 1 non-binding +1 > > > 1 binding -1 > > > 1 non-binding -1 > > > and one (Steve's) vote which I couldn't categorize: 1 (non-binding) > > > > > > Thanks, > > > --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 > > >> > > > > -- > > Arun C. Murthy > > Hortonworks Inc. > > http://hortonworks.com/ > > > > > > > > > -- > http://hortonworks.com/download/ >
