hadoop-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@hortonworks.com>
Subject Re: [VOTE] Release plan for Hadoop 2.0.5
Date Fri, 10 May 2013 00:25:52 GMT

Confused and thought this was dead as the discussion was happening in parallel. I wish this
vote was retracted while the discussion reaches some conclusion.

My concerns:
- As you noted in the by-laws, this plan should also nominate the RM. Or if Arun is doing
this, he should accept this? And may be call the vote for release plan himself? The bylaws
aren't clear about this, but that only seems natural - you manage a release and so you call
for a vote on the plan, no?
- It's not clear what happens of features that are half-way through. That needs to be spelled
- Even otherwise, we can always add features without destabilizing the current release at
all if we can switch the feature off with one flag. Arguable on a case-by-case basis but possible.

- Also,  it isn't always clear what a feature is and what isn't. For e.g, the ResourceManager
restart work in YARN can be called a feature or a bug depending on the context.

In all the above cases, we should discuss on whether a feature can be merged in or not on
a case-by-case basis instead of a blanket no.

-1 (binding)

Side note: The bylaws repeatedly talk of "active committers" and "active PMC members", it
makes sense, but we should clarify that.

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

View raw message