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 maheswara@huawei.com designates
 119.145.14.65 as permitted sender)
From: Uma Maheswara Rao G <maheswara@huawei.com>
To: "general@hadoop.apache.org" <general@hadoop.apache.org>
Subject: RE: [VOTE] Release plan for Hadoop 2.0.5
Thread-Topic: [VOTE] Release plan for Hadoop 2.0.5
Thread-Index: AQHORqWl8qJKyfPtjEyyr8+QyWc6Zpj94wGj
Date: Fri, 10 May 2013 05:03:11 +0000
Message-ID: 
 <1542FA4EE20C5048A5C2A3663BED2A6B319057BE@szxeml561-mbx.china.huawei.com>
References: 
 <CAKtuutGywd26vcy8TJFQhcT3a1E_FQqiqY0vmdFyq2CH-xy+WQ@mail.gmail.com>
In-Reply-To: 
 <CAKtuutGywd26vcy8TJFQhcT3a1E_FQqiqY0vmdFyq2CH-xy+WQ@mail.gmail.com>
Accept-Language: en-US, zh-CN
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

+1
Sounds like a good plan. Having a release with lot of new features with lot=
 of core code changes will really make users afraid to migrate. Initially I=
 was under the impression that branch-2 will be stabilized soon. But the cu=
rrent strategy looks like, it may take some more time. So, having a cut at =
this stage and focusing on stabilization will be a good idea.  Adding new f=
eatures really a great thing and surely each big feature can be included in=
 one one major release as well.

Regards,
Uma =20

________________________________________
From: Konstantin Shvachko [shv.hadoop@gmail.com]
Sent: Thursday, May 02, 2013 1:23 AM
To: general@hadoop.apache.org
Subject: [VOTE] Release plan for Hadoop 2.0.5

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=