Re: [DISCUSS] 2.6.x line releases

[Vinod Kumar Vavilapalli]

It wasn’t a vote. PMC doesn’t vote on code-changes.

It was an extensive community discussion. We arrived at that decision to 
reflect the reality that not many users were running JDK6 anyways at that point 
of time.

Sorry to bust the bubble, this is not one of those things that supports your 
propaganda about how branch-2 is bust.

+Vinod

> On Jul 22, 2016, at 3:59 PM, Allen Wittenauer  
> wrote:
> 
> (It's interesting that ~2 years later, we're still dealing with the fallout 
> of the JRE compatibility break in 2.7.  I wonder how many of those PMCs who 
> voted for it are still actively involved.)

Re: [DISCUSS] 2.6.x line releases

[Sangjin Lee]

Thanks Zhe!

On Fri, Jul 22, 2016 at 4:01 PM, Zhe Zhang 
wrote:

> Thanks for pointing it out Allen. I'll work on an addendum 2.6 patch for
> HADOOP-12800.
>
> On Fri, Jul 22, 2016 at 3:59 PM Allen Wittenauer  >
> wrote:
>
> >
> > > On Jul 22, 2016, at 9:07 AM, Zhe Zhang 
> > wrote:
> > >
> > > Thanks Allen for the note. I thought the 2.6 Dockerfile issue was
> > addressed in https://issues.apache.org/jira/browse/HADOOP-12800?
> >
> > 2.6 builds on JDK6 and JDK7.  2.x, where x>6, builds on JDK7 and JDK8.
> > [1] This should have been a big red flag in that patch:
> >
> > ---
> > +RUN apt-get install -y oracle-java8-installer
> > ---
> >
> > (It's interesting that ~2 years later, we're still dealing with the
> > fallout of the JRE compatibility break in 2.7.  I wonder how many of
> those
> > PMCs who voted for it are still actively involved.)
> >
> > [1] For completeness, 3.x only builds on JDK8 but probably not JDK9,
> given
> > log4j 1.x, etc, etc.
>
> --
> Zhe Zhang
> Apache Hadoop Committer
> http://zhe-thoughts.github.io/about/ | @oldcap
>

Re: [DISCUSS] 2.6.x line releases

[Zhe Zhang]

Thanks for pointing it out Allen. I'll work on an addendum 2.6 patch for
HADOOP-12800.

On Fri, Jul 22, 2016 at 3:59 PM Allen Wittenauer 
wrote:

>
> > On Jul 22, 2016, at 9:07 AM, Zhe Zhang 
> wrote:
> >
> > Thanks Allen for the note. I thought the 2.6 Dockerfile issue was
> addressed in https://issues.apache.org/jira/browse/HADOOP-12800?
>
> 2.6 builds on JDK6 and JDK7.  2.x, where x>6, builds on JDK7 and JDK8.
> [1] This should have been a big red flag in that patch:
>
> ---
> +RUN apt-get install -y oracle-java8-installer
> ---
>
> (It's interesting that ~2 years later, we're still dealing with the
> fallout of the JRE compatibility break in 2.7.  I wonder how many of those
> PMCs who voted for it are still actively involved.)
>
> [1] For completeness, 3.x only builds on JDK8 but probably not JDK9, given
> log4j 1.x, etc, etc.

-- 
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [DISCUSS] 2.6.x line releases

[Allen Wittenauer]

> On Jul 22, 2016, at 9:07 AM, Zhe Zhang  wrote:
> 
> Thanks Allen for the note. I thought the 2.6 Dockerfile issue was addressed 
> in https://issues.apache.org/jira/browse/HADOOP-12800?

2.6 builds on JDK6 and JDK7.  2.x, where x>6, builds on JDK7 and JDK8.  [1] 
This should have been a big red flag in that patch:

---
+RUN apt-get install -y oracle-java8-installer
---

(It's interesting that ~2 years later, we're still dealing with the fallout of 
the JRE compatibility break in 2.7.  I wonder how many of those PMCs who voted 
for it are still actively involved.)

[1] For completeness, 3.x only builds on JDK8 but probably not JDK9, given 
log4j 1.x, etc, etc.  
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] 2.6.x line releases

[Zhe Zhang]

Thanks Allen for the note. I thought the 2.6 Dockerfile issue was addressed
in https://issues.apache.org/jira/browse/HADOOP-12800?

On Fri, Jul 22, 2016 at 9:04 AM Allen Wittenauer 
wrote:

>
> > On Jul 21, 2016, at 5:06 PM, Zhe Zhang 
> wrote:
> >
> > We are using 2.6 releases and would like to see 2.6.5.
> >
> > One related issue, pre-commit is not working for 2.6 (see comment from
> > Allen
> >
> https://issues.apache.org/jira/browse/HDFS-10653?focusedCommentId=15388621=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15388621
> ).
> > Should we fix for the purpose of the release?
>
>
> Someone probably just needs to invest some time in modifying the
> Dockerfile in 2.6 to actually meet the build requirements.  Right now, it's
> way way wrong.

-- 
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [DISCUSS] 2.6.x line releases

[Allen Wittenauer]

> On Jul 21, 2016, at 5:06 PM, Zhe Zhang  wrote:
> 
> We are using 2.6 releases and would like to see 2.6.5.
> 
> One related issue, pre-commit is not working for 2.6 (see comment from
> Allen
> https://issues.apache.org/jira/browse/HDFS-10653?focusedCommentId=15388621=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15388621).
> Should we fix for the purpose of the release?


Someone probably just needs to invest some time in modifying the 
Dockerfile in 2.6 to actually meet the build requirements.  Right now, it's way 
way wrong.
-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] 2.6.x line releases

[Sangjin Lee]

Thanks Chris for stepping up! I'll work with Chris to get started on the
2.6.5 release soon.

Regards,
Sangjin

On Thu, Jul 21, 2016 at 4:43 PM, Chris Trezzo  wrote:

> Sangjin, I would be happy to help you with the work for cutting 2.6.5.
>
> Thanks!
> Chris Trezzo
>
> On Wed, Jul 20, 2016 at 2:44 PM, Akira AJISAKA  >
> wrote:
>
> > Hi Sangjin,
> >
> > I'm thinking it's time for 2.6.5 release. Now there are 51 fixed issues
> in
> > 2.6.5 and the number is more than 2.6.4 (47).
> >
> > > How long do we maintain this line? What would be a sensible EOL policy?
> >
> > Ideally 5 years, because most of our customers in Japan are using Hadoop
> > cluster without upgrading for about 5 years. However, it's probably
> > impossible for us to achieve the long term maintenance in the community
> > because the maintenance cost is too high. Therefore, my answer is "longer
> > is better".
> >
> > By the way, I'm thinking we can reduce the maintenance cost by selecting
> > which branch to maintenance for a long time. An example is Ubuntu LTS.
> > Ubuntu Server LTS is maintained for 5 years but the other releases are
> not.
> >
> > Regards,
> > Akira
> >
> > On 7/20/16 12:45, Sean Busbey wrote:
> >
> >> The HBase community would like more 2.6.z releases.
> >>
> >> On Wed, Jul 20, 2016 at 2:00 PM, Ravi Prakash 
> >> wrote:
> >>
> >>> We for one are not using 2.6.*
> >>>
> >>> On Tue, Jul 19, 2016 at 1:21 PM, Sangjin Lee  wrote:
> >>>
> >>> It's been a while since we had a release on the 2.6.x line. Is it time
> to
>  get ready for a 2.6.5 release? Are folks using and relying on releases
>  on
>  2.6.x? If there is enough interest, I could take that on. Let me know.
> 
>  I also want to gauge the community's interest in maintaining the 2.6.x
>  line. How long do we maintain this line? What would be a sensible EOL
>  policy? Note that as the main code lines start diverging (java
> version,
>  features, etc.), the cost of maintaining multiple release lines does
> go
>  up.
>  I'd love to hear your thoughts.
> 
>  Regards,
>  Sangjin
> 
> 
> >>
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> > For additional commands, e-mail: common-dev-h...@hadoop.apache.org
> >
> >
>

Re: [DISCUSS] 2.6.x line releases

[Zhe Zhang]

We are using 2.6 releases and would like to see 2.6.5.

One related issue, pre-commit is not working for 2.6 (see comment from
Allen
https://issues.apache.org/jira/browse/HDFS-10653?focusedCommentId=15388621=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15388621).
Should we fix for the purpose of the release?

Thanks,

On Thu, Jul 21, 2016 at 5:03 PM Chris Trezzo  wrote:

> Sangjin, I would be happy to help you with the work for cutting 2.6.5.
>
> Thanks!
> Chris Trezzo
>
> On Wed, Jul 20, 2016 at 2:44 PM, Akira AJISAKA  >
> wrote:
>
> > Hi Sangjin,
> >
> > I'm thinking it's time for 2.6.5 release. Now there are 51 fixed issues
> in
> > 2.6.5 and the number is more than 2.6.4 (47).
> >
> > > How long do we maintain this line? What would be a sensible EOL policy?
> >
> > Ideally 5 years, because most of our customers in Japan are using Hadoop
> > cluster without upgrading for about 5 years. However, it's probably
> > impossible for us to achieve the long term maintenance in the community
> > because the maintenance cost is too high. Therefore, my answer is "longer
> > is better".
> >
> > By the way, I'm thinking we can reduce the maintenance cost by selecting
> > which branch to maintenance for a long time. An example is Ubuntu LTS.
> > Ubuntu Server LTS is maintained for 5 years but the other releases are
> not.
> >
> > Regards,
> > Akira
> >
> > On 7/20/16 12:45, Sean Busbey wrote:
> >
> >> The HBase community would like more 2.6.z releases.
> >>
> >> On Wed, Jul 20, 2016 at 2:00 PM, Ravi Prakash 
> >> wrote:
> >>
> >>> We for one are not using 2.6.*
> >>>
> >>> On Tue, Jul 19, 2016 at 1:21 PM, Sangjin Lee  wrote:
> >>>
> >>> It's been a while since we had a release on the 2.6.x line. Is it time
> to
>  get ready for a 2.6.5 release? Are folks using and relying on releases
>  on
>  2.6.x? If there is enough interest, I could take that on. Let me know.
> 
>  I also want to gauge the community's interest in maintaining the 2.6.x
>  line. How long do we maintain this line? What would be a sensible EOL
>  policy? Note that as the main code lines start diverging (java
> version,
>  features, etc.), the cost of maintaining multiple release lines does
> go
>  up.
>  I'd love to hear your thoughts.
> 
>  Regards,
>  Sangjin
> 
> 
> >>
> >>
> >>
> >
> > -
> > To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> > For additional commands, e-mail: common-dev-h...@hadoop.apache.org
> >
> >
>
-- 
Zhe Zhang
Apache Hadoop Committer
http://zhe-thoughts.github.io/about/ | @oldcap

Re: [DISCUSS] 2.6.x line releases

[Chris Trezzo]

Sangjin, I would be happy to help you with the work for cutting 2.6.5.

Thanks!
Chris Trezzo

On Wed, Jul 20, 2016 at 2:44 PM, Akira AJISAKA 
wrote:

> Hi Sangjin,
>
> I'm thinking it's time for 2.6.5 release. Now there are 51 fixed issues in
> 2.6.5 and the number is more than 2.6.4 (47).
>
> > How long do we maintain this line? What would be a sensible EOL policy?
>
> Ideally 5 years, because most of our customers in Japan are using Hadoop
> cluster without upgrading for about 5 years. However, it's probably
> impossible for us to achieve the long term maintenance in the community
> because the maintenance cost is too high. Therefore, my answer is "longer
> is better".
>
> By the way, I'm thinking we can reduce the maintenance cost by selecting
> which branch to maintenance for a long time. An example is Ubuntu LTS.
> Ubuntu Server LTS is maintained for 5 years but the other releases are not.
>
> Regards,
> Akira
>
> On 7/20/16 12:45, Sean Busbey wrote:
>
>> The HBase community would like more 2.6.z releases.
>>
>> On Wed, Jul 20, 2016 at 2:00 PM, Ravi Prakash 
>> wrote:
>>
>>> We for one are not using 2.6.*
>>>
>>> On Tue, Jul 19, 2016 at 1:21 PM, Sangjin Lee  wrote:
>>>
>>> It's been a while since we had a release on the 2.6.x line. Is it time to
 get ready for a 2.6.5 release? Are folks using and relying on releases
 on
 2.6.x? If there is enough interest, I could take that on. Let me know.

 I also want to gauge the community's interest in maintaining the 2.6.x
 line. How long do we maintain this line? What would be a sensible EOL
 policy? Note that as the main code lines start diverging (java version,
 features, etc.), the cost of maintaining multiple release lines does go
 up.
 I'd love to hear your thoughts.

 Regards,
 Sangjin


>>
>>
>>
>
> -
> To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
> For additional commands, e-mail: common-dev-h...@hadoop.apache.org
>
>

Re: [DISCUSS] 2.6.x line releases

[Akira AJISAKA]

Hi Sangjin,

I'm thinking it's time for 2.6.5 release. Now there are 51 fixed issues 
in 2.6.5 and the number is more than 2.6.4 (47).


> How long do we maintain this line? What would be a sensible EOL policy?

Ideally 5 years, because most of our customers in Japan are using Hadoop 
cluster without upgrading for about 5 years. However, it's probably 
impossible for us to achieve the long term maintenance in the community 
because the maintenance cost is too high. Therefore, my answer is 
"longer is better".


By the way, I'm thinking we can reduce the maintenance cost by selecting 
which branch to maintenance for a long time. An example is Ubuntu LTS. 
Ubuntu Server LTS is maintained for 5 years but the other releases are not.


Regards,
Akira

On 7/20/16 12:45, Sean Busbey wrote:

The HBase community would like more 2.6.z releases.

On Wed, Jul 20, 2016 at 2:00 PM, Ravi Prakash  wrote:

We for one are not using 2.6.*

On Tue, Jul 19, 2016 at 1:21 PM, Sangjin Lee  wrote:


It's been a while since we had a release on the 2.6.x line. Is it time to
get ready for a 2.6.5 release? Are folks using and relying on releases on
2.6.x? If there is enough interest, I could take that on. Let me know.

I also want to gauge the community's interest in maintaining the 2.6.x
line. How long do we maintain this line? What would be a sensible EOL
policy? Note that as the main code lines start diverging (java version,
features, etc.), the cost of maintaining multiple release lines does go up.
I'd love to hear your thoughts.

Regards,
Sangjin








-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] 2.6.x line releases

[Sean Busbey]

The HBase community would like more 2.6.z releases.

On Wed, Jul 20, 2016 at 2:00 PM, Ravi Prakash  wrote:
> We for one are not using 2.6.*
>
> On Tue, Jul 19, 2016 at 1:21 PM, Sangjin Lee  wrote:
>
>> It's been a while since we had a release on the 2.6.x line. Is it time to
>> get ready for a 2.6.5 release? Are folks using and relying on releases on
>> 2.6.x? If there is enough interest, I could take that on. Let me know.
>>
>> I also want to gauge the community's interest in maintaining the 2.6.x
>> line. How long do we maintain this line? What would be a sensible EOL
>> policy? Note that as the main code lines start diverging (java version,
>> features, etc.), the cost of maintaining multiple release lines does go up.
>> I'd love to hear your thoughts.
>>
>> Regards,
>> Sangjin
>>



-- 
busbey

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org

Re: [DISCUSS] 2.6.x line releases

[Ravi Prakash]

We for one are not using 2.6.*

On Tue, Jul 19, 2016 at 1:21 PM, Sangjin Lee  wrote:

> It's been a while since we had a release on the 2.6.x line. Is it time to
> get ready for a 2.6.5 release? Are folks using and relying on releases on
> 2.6.x? If there is enough interest, I could take that on. Let me know.
>
> I also want to gauge the community's interest in maintaining the 2.6.x
> line. How long do we maintain this line? What would be a sensible EOL
> policy? Note that as the main code lines start diverging (java version,
> features, etc.), the cost of maintaining multiple release lines does go up.
> I'd love to hear your thoughts.
>
> Regards,
> Sangjin
>

[DISCUSS] 2.6.x line releases

[Sangjin Lee]

It's been a while since we had a release on the 2.6.x line. Is it time to
get ready for a 2.6.5 release? Are folks using and relying on releases on
2.6.x? If there is enough interest, I could take that on. Let me know.

I also want to gauge the community's interest in maintaining the 2.6.x
line. How long do we maintain this line? What would be a sensible EOL
policy? Note that as the main code lines start diverging (java version,
features, etc.), the cost of maintaining multiple release lines does go up.
I'd love to hear your thoughts.

Regards,
Sangjin