Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Hadoop, mail # general - [RESULT] Release plan for Hadoop 2.0.5


Copy link to this message
-
RE: [RESULT] Release plan for Hadoop 2.0.5
Bikas Saha 2013-05-14, 20:59
I thought I saw an email from Chris Douglas explaining why this vote may
not be valid? What is the resolution?

-----Original Message-----
From: Arpit Gupta [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, May 14, 2013 1:54 PM
To: [EMAIL PROTECTED]
Subject: Re: [RESULT] Release plan for Hadoop 2.0.5

I was not aware that committers had binding vote on this. Can i still
vote? Or can the vote be extended?

--
Arpit Gupta
Hortonworks Inc.
http://hortonworks.com/

On May 14, 2013, at 1:15 PM, Vinod Kumar Vavilapalli
<[EMAIL PROTECTED]> wrote:

>
> The vote count is wrong:
>
> 6 binding +1s
> 5 binding -1s
> 4 non-binding +1s
> 2 non-binding -1s.
>
> I think you mis-counted stevel, whose vote is binding.
>
> On May 14, 2013, at 10:07 AM, Konstantin Shvachko wrote:
>
>> This vote passes with
>> 6 binding +1s
>> 4 non-binding +1
>> 4 binding -1
>> 3 non-binding -1
>>
>> Thank you for voting,
>> --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
>>>
>