Is it time to do a release?

[Steve Loughran <st...@hortonworks.com>]

1. What do we have to do before pushing out a new release?

2. Should we stay with Hadoop 2.6 vs 2.7.1? And if 2.6, shall we make it the last 2.6-compatible version?

Re: Is it time to do a release?

[Gour Saha <gs...@hortonworks.com>]

Thanks Steve. 

Minor change, I changed it to 0.81.0 instead of 0.80.1. I use the no after
the 2nd dot to represent the RC candidates for a specific release (like we
needed for 0.70.1).

We already have the 0.81.0 version created in the jira and bugs assigned
to it as well.

-Gour

On 9/18/15, 1:55 AM, "Steve Loughran" <st...@hortonworks.com> wrote:

>
>> On 16 Sep 2015, at 21:49, Gour Saha <gs...@hortonworks.com> wrote:
>> 
>> +1 for doing a release.
>> 
>> But I think it should be released as 0.81.0 and not 0.90.0. I might be
>> wrong, but I think there weren¹t any significant work done post 0.80, on
>> adding new features. There were quite a few bug fixes for sure,
>>including
>> fixes to the tech-preview version of docker support that went out in
>>0.80.
>> 
>> Thoughts?
>> 
>> -Gour
>
>
>OK: renamed the JIRA https://issues.apache.org/jira/browse/SLIDER-937
>

Re: Is it time to do a release?

[Steve Loughran <st...@hortonworks.com>]

> On 16 Sep 2015, at 21:49, Gour Saha <gs...@hortonworks.com> wrote:
> 
> +1 for doing a release.
> 
> But I think it should be released as 0.81.0 and not 0.90.0. I might be
> wrong, but I think there weren¹t any significant work done post 0.80, on
> adding new features. There were quite a few bug fixes for sure, including
> fixes to the tech-preview version of docker support that went out in 0.80.
> 
> Thoughts?
> 
> -Gour


OK: renamed the JIRA https://issues.apache.org/jira/browse/SLIDER-937

Re: Is it time to do a release?

[Gour Saha <gs...@hortonworks.com>]

+1 for doing a release.

But I think it should be released as 0.81.0 and not 0.90.0. I might be
wrong, but I think there weren¹t any significant work done post 0.80, on
adding new features. There were quite a few bug fixes for sure, including
fixes to the tech-preview version of docker support that went out in 0.80.

Thoughts?

-Gour

On 9/16/15, 9:19 AM, "Jon Maron" <jm...@hortonworks.com> wrote:

>
>> On Sep 16, 2015, at 12:11 PM, Josh Elser <jo...@gmail.com> wrote:
>> 
>> Steve Loughran wrote:
>>> 1. What do we have to do before pushing out a new release?
>>> 
>>> 2. Should we stay with Hadoop 2.6 vs 2.7.1? And if 2.6, shall we make
>>> it the last 2.6-compatible version?
>> 
>> +1 for a new release.
>
>+1
>
>> 
>> IMO, we should try to keep compatibility with 2.6 (and 2.7) until
>>there's a compelling reason not to :)
>> 
>
>And another +1 ;)
>

Re: Is it time to do a release?

[Jon Maron <jm...@hortonworks.com>]

> On Sep 16, 2015, at 12:11 PM, Josh Elser <jo...@gmail.com> wrote:
> 
> Steve Loughran wrote:
>> 1. What do we have to do before pushing out a new release?
>> 
>> 2. Should we stay with Hadoop 2.6 vs 2.7.1? And if 2.6, shall we make
>> it the last 2.6-compatible version?
> 
> +1 for a new release.

+1

> 
> IMO, we should try to keep compatibility with 2.6 (and 2.7) until there's a compelling reason not to :)
> 

And another +1 ;)

Re: Is it time to do a release?

[Yu Liu <yl...@hortonworks.com>]

+1 for a new release
________________________________________
From: Josh Elser <jo...@gmail.com>
Sent: Wednesday, September 16, 2015 9:11 AM
To: dev@slider.incubator.apache.org
Subject: Re: Is it time to do a release?

Steve Loughran wrote:
> 1. What do we have to do before pushing out a new release?
>
> 2. Should we stay with Hadoop 2.6 vs 2.7.1? And if 2.6, shall we make
> it the last 2.6-compatible version?

+1 for a new release.

IMO, we should try to keep compatibility with 2.6 (and 2.7) until
there's a compelling reason not to :)

Re: Is it time to do a release?

[Josh Elser <jo...@gmail.com>]

Steve Loughran wrote:
> 1. What do we have to do before pushing out a new release?
>
> 2. Should we stay with Hadoop 2.6 vs 2.7.1? And if 2.6, shall we make
> it the last 2.6-compatible version?

+1 for a new release.

IMO, we should try to keep compatibility with 2.6 (and 2.7) until 
there's a compelling reason not to :)