Mailing-List: contact general-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: general@hadoop.apache.org
Received-SPF: pass (nike.apache.org: domain of lohit.vijayarenu@gmail.com
 designates 209.85.219.46 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAB7mwtFfFQMTqG7_+LqbWGKHuhdv+au-6eeBcWVqqrQ14jypag@mail.gmail.com>
References: 
 <CAKtuutGywd26vcy8TJFQhcT3a1E_FQqiqY0vmdFyq2CH-xy+WQ@mail.gmail.com>
	<D2D44908-B9E1-4337-8D06-08F086FDEE77@apache.org>
	<CAB7mwtFfFQMTqG7_+LqbWGKHuhdv+au-6eeBcWVqqrQ14jypag@mail.gmail.com>
Date: Thu, 9 May 2013 19:58:25 -0700
Message-ID: 
 <CA+01ahiV0HiYjU1vpz8ZND-Q3A=S5k8OwicdjGw5x+Jg_j_jFQ@mail.gmail.com>
Subject: Re: [VOTE] Release plan for Hadoop 2.0.5
From: lohit <lohit.vijayarenu@gmail.com>
To: general@hadoop.apache.org
Content-Type: multipart/alternative; boundary=089e0149ca5c3b740f04dc545740

--089e0149ca5c3b740f04dc545740
Content-Type: text/plain; charset=UTF-8

+1
Particularly making 2.0.X stable will help wider adoption sooner.


2013/5/9 J. Rottinghuis <jrottinghuis@gmail.com>

> +1 (non-binding) to stabilize 2.0, and add new features only after a stable
> release.
> I understand that what constitutes as "new feature" versus "stabilizing" is
> subjective.
>
> Thanks,
>
> Joep
>
> On May 1, 2013, at 12:53 PM, Konstantin Shvachko 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
> >
> >
>


-- 
Have a Nice Day!
Lohit

--089e0149ca5c3b740f04dc545740--