Re: [Release thread] 2.6.5 release activities

We have now cut branch-2.6.5. On Wed, Sep 14, 2016 at 4:38 PM, Sangjin Lee wrote: > We ported 16 issues to branch-2.6. We will go ahead and start the release > process, including cutting the release branch. If you have any critical > change that should be made part of 2.6.5,

Re: [Release thread] 2.6.5 release activities

We ported 16 issues to branch-2.6. We will go ahead and start the release process, including cutting the release branch. If you have any critical change that should be made part of 2.6.5, please reach out to us and commit the changes. Thanks! Sangjin On Mon, Sep 12, 2016 at 3:24 PM, Sangjin Lee

Re: [Release thread] 2.6.5 release activities

Thanks Chris! I'll help Chris to get those JIRAs marked in his spreadsheet committed. We'll cut the release branch shortly after that. If you have any critical change that should be made part of 2.6.5 (CVE patches included), please reach out to us and commit the changes. If all things go well,

Re: [Release thread] 2.6.5 release activities

Hi all, I wanted to give an update on the Hadoop 2.6.5 release efforts. Here is what has been done so far: 1. I have gone through all of the potential backports and recorded the commit hashes for each of them from the branch that seems the most appropriate (i.e. if there was a backport to 2.7.x

Re: [Release thread] 2.6.5 release activities

> On Aug 12, 2016, at 8:19 AM, Junping Du wrote: > > In this community, we are so aggressive to drop Java 7 support in 3.0.x > release. Here, why we are so conservative to keep releasing new bits to > support Java 6? I don't view a group of people putting bug

Re: [Release thread] 2.6.5 release activities

> On 12 Aug 2016, at 01:42, Chris Trezzo wrote: > > Thanks everyone for the discussion! Based on what has been said in this > thread, I will move forward on the preparation efforts (working with > Sangjin and the community) for a 2.6.5 release. If there is a strong >

Re: [Release thread] 2.6.5 release activities

M > To: Karthik Kambatla > Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org > Subject: Re: [Release thread] 2.6.5 release activities > > Thanks everyone for the discussion! Based on what has been said in this > t

Re: [Release thread] 2.6.5 release activities

.@hadoop.apache.org>; "yarn-...@hadoop.apache.org" <yarn-...@hadoop.apache.org> Sent: Thursday, August 11, 2016 6:42 PM Subject: Re: [Release thread] 2.6.5 release activities Thanks everyone for the discussion! Based on what has been said in this thread, I will move forward on the prep

Re: [Release thread] 2.6.5 release activities

From: Chris Trezzo <ctre...@gmail.com> Sent: Friday, August 12, 2016 12:42 AM To: Karthik Kambatla Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: [Release thread] 2.6.5 release activities Thanks ev

Re: [Release thread] 2.6.5 release activities

Thanks everyone for the discussion! Based on what has been said in this thread, I will move forward on the preparation efforts (working with Sangjin and the community) for a 2.6.5 release. If there is a strong objection to this, please let us know. I see three initial tasks going forward: 1. Fix

Re: [Release thread] 2.6.5 release activities

Since there is sufficient interest in 2.6.5, we should probably do it. All the reasons Allen outlines make sense. That said, Junping brings up a very important point that we should think of for future releases. For a new user or a user that does not directly contribute to the project, more stable

Re: [Release thread] 2.6.5 release activities

> On Aug 11, 2016, at 8:10 AM, Junping Du wrote: > > Allen, to be clear, I am not against any branch release effort here. However, "I'm not an X but " > as RM for previous releases 2.6.3 and 2.6.4, I feel to have responsibility to > take care

Re: [Release thread] 2.6.5 release activities

reduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: [Release thread] 2.6.5 release activities > On Aug 11, 2016, at 5:59 AM, Junping Du <j...@hortonworks.com> wrote: > > These comments are more like wishes but not giving more clarifications > on the needs. I

Re: [Release thread] 2.6.5 release activities

> On Aug 11, 2016, at 5:59 AM, Junping Du wrote: > > These comments are more like wishes but not giving more clarifications > on the needs. I would like to hear more specific reasons to not move to 2.7.x > releases but prefer to upgrade to 2.6.5. If the only reason

Re: [Release thread] 2.6.5 release activities

ris Trezzo <ctre...@gmail.com> Sent: Wednesday, August 10, 2016 9:30 PM To: Junping Du Cc: common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Jason Lowe Subject: Re: [Release thread] 2.6.5 release activities Thanks J

Re: [Release thread] 2.6.5 release activities

> Sent: Wednesday, August 10, 2016 4:14 PM > To: Chris Trezzo; common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; > mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org > Subject: Re: [Release thread] 2.6.5 release activities > > Thanks for organizing this, Chris! > I don't believe H

Re: [Release thread] 2.6.5 release activities

hoo-inc.com.INVALID> Sent: Wednesday, August 10, 2016 4:14 PM To: Chris Trezzo; common-dev@hadoop.apache.org; hdfs-...@hadoop.apache.org; mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org Subject: Re: [Release thread] 2.6.5 release activities Thanks for organizing this, Chris! I don't b

Re: [Release thread] 2.6.5 release activities

e.org" <yarn-...@hadoop.apache.org> Sent: Tuesday, August 9, 2016 7:32 PM Subject: [Release thread] 2.6.5 release activities Based on the sentiment in the "[DISCUSS] 2.6.x line releases" thread, I have moved forward with some of the initial effort in creating a 2.6.5 releas

[Release thread] 2.6.5 release activities

Based on the sentiment in the "[DISCUSS] 2.6.x line releases" thread, I have moved forward with some of the initial effort in creating a 2.6.5 release. I am forking this thread so we have a dedicated 2.6.5 release thread. I have gone through the git logs and gathered a list of JIRAs that are in