hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@hortonworks.com>
Subject Re: [DISCUSS] Looking to a 2.8.0 release
Date Tue, 21 Apr 2015 23:59:26 GMT

Sure, I agree it's better to have clear guidelines and scheme. Let me fork this thread about
that.

Re 2.7.0, I just forgot about the naming initially though I was clear in the discussion/voting.
I so had to end up calling it alpha outside of the release artifact naming.

Thanks
+Vinod

On Apr 21, 2015, at 4:26 PM, Andrew Wang <andrew.wang@cloudera.com> wrote:

> I would also like to support Karthik's proposal on the release thread about
> version numbering. 2.7.0 being "alpha" is pretty confusing since all of the
> other 2.x releases since GA have been stable. I think users would prefer a
> version like "2.8.0-alpha1" instead, which is very clear and similar to
> what we did for 2.0 and 2.1. Then we release 2.8.0 when we're actually
> stable.
> 
> I don't know if it's retroactively possible to do this for 2.7.0, but it's
> something to consider for the next 2.7 alpha or beta or whatever.
> 
> On Tue, Apr 21, 2015 at 3:12 PM, Karthik Kambatla <kasha@cloudera.com>
> wrote:
> 
>> The feature set here seems pretty long, even for 2 - 3 months. Can we come
>> up with a minimum set of features (or a number of features) that justify a
>> new minor release, and start stabilizing as soon as those are in?
>> 
>> On Tue, Apr 21, 2015 at 2:39 PM, Vinod Kumar Vavilapalli <
>> vinodkv@apache.org
>>> wrote:
>> 
>>> With 2.7.0 out of the way, and with more maintenance releases to
>> stabilize
>>> it, I propose we start thinking about 2.8.0.
>>> 
>>> Here's my first cut of the proposal, will update the Roadmap wiki.
>>> - Support *both* JDK7 and JDK8 runtimes: HADOOP-11090
>>> - Compatibility tools to catch backwards, forwards compatibility issues
>> at
>>> patch submission, release times. Some of it is captured at YARN-3292.
>> This
>>> also involves resurrecting jdiff (HADOOP-11776/YARN-3426/MAPREDUCE-6310)
>>> and/or investing in new tools.
>>> - HADOOP-11656 Classpath isolation for downstream clients
>>> - Support for Erasure Codes in HDFS HDFS-7285
>>> - Early work for disk and network isolation in YARN: YARN-2139,
>> YARN-2140
>>> - YARN Timeline Service Next generation: YARN-2928. At least
>> branch-merge
>>> + early peek.
>>> - Supporting non-exclusive node-labels: YARN-3214
>>> 
>>> I'm experimenting with more agile 2.7.x releases and would like to
>> continue
>>> the same by volunteering as the RM for 2.8.x too.
>>> 
>>> Given the long time we took with 2.7.0, the timeline I am looking at is
>>> 8-12 weeks. We can pick as many features as they finish along and make a
>>> more predictable releases instead of holding up releases for ever.
>>> 
>>> Thoughts?
>>> 
>>> Thanks
>>> +Vinod
>>> 
>> 
>> 
>> 
>> --
>> Karthik Kambatla
>> Software Engineer, Cloudera Inc.
>> --------------------------------------------
>> http://five.sentenc.es
>> 


Mime
View raw message