Thanks Vinod. +1 for 2.8 release start.

Regards,
Uma

On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" <vino...@apache.org> wrote:

>Seems like all the features listed in the Roadmap wiki are in. I¹m going
>to try cutting an RC this weekend for a first/non-stable release off of
>branch-2.8.
>
>Let me know if anyone has any objections/concerns.
>
>Thanks
>+Vinod
>
>> On Nov 25, 2015, at 5:59 PM, Vinod Kumar Vavilapalli
>><vino...@apache.org> wrote:
>> 
>> Branch-2.8 is created.
>> 
>> As mentioned before, the goal on branch-2.8 is to put improvements /
>>fixes to existing features with a goal of converging on an alpha release
>>soon.
>> 
>> Thanks
>> +Vinod
>> 
>> 
>>> On Nov 25, 2015, at 5:30 PM, Vinod Kumar Vavilapalli
>>><vino...@apache.org> wrote:
>>> 
>>> Forking threads now in order to track all things related to the
>>>release.
>>> 
>>> Creating the branch now.
>>> 
>>> Thanks
>>> +Vinod
>>> 
>>> 
>>>> On Nov 25, 2015, at 11:37 AM, Vinod Kumar Vavilapalli
>>>><vino...@apache.org> wrote:
>>>> 
>>>> I think we¹ve converged at a high level w.r.t 2.8. And as I just sent
>>>>out an email, I updated the Roadmap wiki reflecting the same:
>>>>https://wiki.apache.org/hadoop/Roadmap
>>>><https://wiki.apache.org/hadoop/Roadmap>
>>>> 
>>>> I plan to create a 2.8 branch EOD today.
>>>> 
>>>> The goal for all of us should be to restrict improvements & fixes to
>>>>only (a) the feature-set documented under 2.8 in the RoadMap wiki and
>>>>(b) other minor features that are already in 2.8.
>>>> 
>>>> Thanks
>>>> +Vinod
>>>> 
>>>> 
>>>>> On Nov 11, 2015, at 12:13 PM, Vinod Kumar Vavilapalli
>>>>><vino...@hortonworks.com <mailto:vino...@hortonworks.com>> wrote:
>>>>> 
>>>>> - Cut a branch about two weeks from now
>>>>> - Do an RC mid next month (leaving ~4weeks since branch-cut)
>>>>> - As with 2.7.x series, the first release will still be called as
>>>>>early / alpha release in the interest of
>>>>>   ‹ gaining downstream adoption
>>>>>   ‹ wider testing,
>>>>>   ‹ yet reserving our right to fix any inadvertent incompatibilities
>>>>>introduced.
>>>> 
>>> 
>> 
>

Reply via email to