hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Konstantin Boudnik <...@apache.org>
Subject Re: [VOTE] Release plan for Hadoop 2.0.5
Date Tue, 07 May 2013 03:28:26 GMT
Yes, I will be still +1 because there's no other way of fully testing
compatibility of Hadoop with downstream projects but using Bigtop.

Cos

On Sat, May 04, 2013 at 03:21PM, Tsz Wo Sze wrote:
> Then, would you still +1 without the addition?═ If yes, you should -1 on this VOTE.
> Tsz-Wo
> 
> ________________________________
>  From: Konstantin Boudnik <cos@apache.org>
> To: general@hadoop.apache.org 
> Sent: Thursday, May 2, 2013 8:40 PM
> Subject: Re: [VOTE] Release plan for Hadoop 2.0.5
>  
> 
> +1 with one addition I'd like to make to the plan
> 
> ═ - making downstream testing a passing criteria for the release. I don't mean
> ═ ═ that Hadoop community needs to be responsible for testing of _all_
> ═ ═ downstream components. What I'd like to see is a practice we used in the
> ═ ═ 2.0.4-alpha with Bigtop 0.6 where passage of the tests in the latter was
> ═ ═ a, perhaps unofficial, release criteria for the former.
> 
> I also agree with 2.0.5 versioning, because essentially, future stability of
> the API - of freezing - is the solid base we all are looking for.
> 
> Cos
> 
> On Wed, May 01, 2013 at 12:53PM, 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

Mime
View raw message