subject:"\[Release thread\] 2.8.0 release activities"

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-20 Thread Andrew Wang

After some googling, I discovered we need the sign profile to make deploy
work:

mvn deploy -Psign -DskipTests -DskipShading

Updated HowToRelease accordingly.

On Fri, Jan 20, 2017 at 11:15 AM, Andrew Wang 
wrote:

> What I meant is that you can mvn deploy the specific missing files to fix
> up the repo state. Though we should also figure out why the deploy plugin
> didn't pick up the signature files the first time.
>
> Best,
> Andrew
>
> On Fri, Jan 20, 2017 at 11:12 AM, Junping Du  wrote:
>
>> Yes. I did maven deploy in root directory before close the staging
>> repository. If this is the only suspect, I can drop the repository and do
>> mvn deploy again.
>>
>>
>> Thanks,
>>
>>
>> Junping
>> --
>> *From:* Andrew Wang 
>> *Sent:* Friday, January 20, 2017 10:48 AM
>> *To:* Junping Du
>> *Cc:* common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>>
>> *Subject:* Re: [Continued] [Release thread] 2.8.0 release activities
>>
>> You can check the error message by clicking on it, a bunch like this:
>>
>> Missing Signature: '/org/apache/hadoop/hadoop-map
>> reduce-client-jobclient/2.8.0/hadoop-mapreduce-client-jobclient-2.8.0-tests.jar.asc'
>> does not exist for 'hadoop-mapreduce-client-jobclient-2.8.0-tests.jar'.
>>
>> Did you maven deploy all the signature files?
>>
>> On Fri, Jan 20, 2017 at 2:04 AM, Junping Du  wrote:
>>
>>> Hi,
>>> I have successfully built the release bit on branch-2.8.0 by
>>> following: https://wiki.apache.org/hadoop/HowToRelease step by step.
>>> However, when try to close the "Staging Repositories" at Nexus page (
>>> https://repository.apache.org/#stagingRepositories), I found our
>>> repository - orgapachehadoop-1051 cannot be closed due to some signature
>>> validation failed and one Apache rule failed. I never met this problem
>>> before in previous releasing 2.6.3 and 2.6.4. Is this related to our recent
>>> changes on release process/tools (docker based)? Any ideas or thoughts on
>>> how to fix the problem?
>>>
>>> Thanks,
>>>
>>> Junping
>>>
>>> 
>>> From: Junping Du 
>>> Sent: Thursday, January 19, 2017 6:46 PM
>>> To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
>>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>>> Cc: Varun Vasudev
>>> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>>>
>>> According to Varun's offline email, the security fixes has landed on
>>> branch-2, 2.8 and 2.8.0 branch.
>>> I was kicking off a new RC build (RC1), and will publish it for vote
>>> soon. In the mean time, please mark fix version as 2.8.1 for any new
>>> commits landed on branch-2.8, and don't commit anything to branch-2.8.0 at
>>> this moment. Thanks!
>>>
>>> Cheers,
>>>
>>> Junping
>>>
>>> 
>>> From: Junping Du 
>>> Sent: Wednesday, January 18, 2017 3:26 PM
>>> To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
>>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>>> Cc: Varun Vasudev
>>> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>>>
>>> Hi folks,
>>>  In the passed one or two weeks, we found some new blockers get
>>> coming on branch-2.8, like: YARN-6068 (log aggregation get stuck when NM
>>> restart with work preserving enabled) and YARN-6072 (RM unable to start in
>>> secure mode). Both of them are fixed now (YARN-6072 is fixed by Ajith and I
>>> fixed YARN-6068), and I was starting the RC build process since early this
>>> week. As we have significant build tools/process change (docker based)
>>> since 2.8 comparing with 2.6/2.7, it takes me a while to get familiar with
>>> it and finally get a successful build on 2.8.0-RC0 last night.
>>>  I already push RC0 tag into public which is prerequisite step
>>> before RC voting. However,  in the mean while, I was pinged by Varun
>>> Vasudev that there are a known vulnerability issues on container_executor
>>> get identified and discussed in hadoop security email threads - looks like
>>> YARN-5704 fixed part of it, but left part - the privilege escalation via
>>> /proc/self/environ is not fixed yet. So most likely, I have

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-20 Thread Allen Wittenauer

If you ran mvn clean at any point in your repo between create-release and mvn 
deploy, you'll need to start at running create-release again.  create-release 
leaves things in a state that mvn deploy should be ready to go, with no clean 
necessary.


> On Jan 20, 2017, at 11:12 AM, Junping Du  wrote:
> 
> Yes. I did maven deploy in root directory before close the staging 
> repository. If this is the only suspect, I can drop the repository and do mvn 
> deploy again.
> 
> 
> Thanks,
> 
> 
> Junping
> 
> 
> From: Andrew Wang 
> Sent: Friday, January 20, 2017 10:48 AM
> To: Junping Du
> Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
> 
> You can check the error message by clicking on it, a bunch like this:
> 
> Missing Signature: 
> '/org/apache/hadoop/hadoop-mapreduce-client-jobclient/2.8.0/hadoop-mapreduce-client-jobclient-2.8.0-tests.jar.asc'
>  does not exist for 'hadoop-mapreduce-client-jobclient-2.8.0-tests.jar'.
> 
> Did you maven deploy all the signature files?
> 
> On Fri, Jan 20, 2017 at 2:04 AM, Junping Du 
> mailto:j...@hortonworks.com>> wrote:
> Hi,
>I have successfully built the release bit on branch-2.8.0 by following: 
> https://wiki.apache.org/hadoop/HowToRelease step by step. However, when try 
> to close the "Staging Repositories" at Nexus page 
> (https://repository.apache.org/#stagingRepositories), I found our repository 
> - orgapachehadoop-1051 cannot be closed due to some signature validation 
> failed and one Apache rule failed. I never met this problem before in 
> previous releasing 2.6.3 and 2.6.4. Is this related to our recent changes on 
> release process/tools (docker based)? Any ideas or thoughts on how to fix the 
> problem?
> 
> Thanks,
> 
> Junping
> 
> 
> From: Junping Du mailto:j...@hortonworks.com>>
> Sent: Thursday, January 19, 2017 6:46 PM
> To: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
> hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
> mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
> yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>
> Cc: Varun Vasudev
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
> 
> According to Varun's offline email, the security fixes has landed on 
> branch-2, 2.8 and 2.8.0 branch.
> I was kicking off a new RC build (RC1), and will publish it for vote soon. In 
> the mean time, please mark fix version as 2.8.1 for any new commits landed on 
> branch-2.8, and don't commit anything to branch-2.8.0 at this moment. Thanks!
> 
> Cheers,
> 
> Junping
> 
> 
> From: Junping Du mailto:j...@hortonworks.com>>
> Sent: Wednesday, January 18, 2017 3:26 PM
> To: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
> hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
> mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
> yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>
> Cc: Varun Vasudev
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
> 
> Hi folks,
> In the passed one or two weeks, we found some new blockers get coming on 
> branch-2.8, like: YARN-6068 (log aggregation get stuck when NM restart with 
> work preserving enabled) and YARN-6072 (RM unable to start in secure mode). 
> Both of them are fixed now (YARN-6072 is fixed by Ajith and I fixed 
> YARN-6068), and I was starting the RC build process since early this week. As 
> we have significant build tools/process change (docker based) since 2.8 
> comparing with 2.6/2.7, it takes me a while to get familiar with it and 
> finally get a successful build on 2.8.0-RC0 last night.
> I already push RC0 tag into public which is prerequisite step before RC 
> voting. However,  in the mean while, I was pinged by Varun Vasudev that there 
> are a known vulnerability issues on container_executor get identified and 
> discussed in hadoop security email threads - looks like YARN-5704 fixed part 
> of it, but left part - the privilege escalation via /proc/self/environ is not 
> fixed yet. So most likely, I have to withdraw our 2.8.0 RC0 although I 
> haven't announced it public for vote yet. I will wait this issue get fixed to 
> prepare a new release candidate. As RC0 tag cannot be reverted after push 
> into apache, our next release candidate will start from RC1.
>As

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-20 Thread Andrew Wang

What I meant is that you can mvn deploy the specific missing files to fix
up the repo state. Though we should also figure out why the deploy plugin
didn't pick up the signature files the first time.

Best,
Andrew

On Fri, Jan 20, 2017 at 11:12 AM, Junping Du  wrote:

> Yes. I did maven deploy in root directory before close the staging
> repository. If this is the only suspect, I can drop the repository and do
> mvn deploy again.
>
>
> Thanks,
>
>
> Junping
> --
> *From:* Andrew Wang 
> *Sent:* Friday, January 20, 2017 10:48 AM
> *To:* Junping Du
> *Cc:* common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>
> *Subject:* Re: [Continued] [Release thread] 2.8.0 release activities
>
> You can check the error message by clicking on it, a bunch like this:
>
> Missing Signature: '/org/apache/hadoop/hadoop-
> mapreduce-client-jobclient/2.8.0/hadoop-mapreduce-client-jobclient-2.8.0-tests.jar.asc'
> does not exist for 'hadoop-mapreduce-client-jobclient-2.8.0-tests.jar'.
>
> Did you maven deploy all the signature files?
>
> On Fri, Jan 20, 2017 at 2:04 AM, Junping Du  wrote:
>
>> Hi,
>> I have successfully built the release bit on branch-2.8.0 by
>> following: https://wiki.apache.org/hadoop/HowToRelease step by step.
>> However, when try to close the "Staging Repositories" at Nexus page (
>> https://repository.apache.org/#stagingRepositories), I found our
>> repository - orgapachehadoop-1051 cannot be closed due to some signature
>> validation failed and one Apache rule failed. I never met this problem
>> before in previous releasing 2.6.3 and 2.6.4. Is this related to our recent
>> changes on release process/tools (docker based)? Any ideas or thoughts on
>> how to fix the problem?
>>
>> Thanks,
>>
>> Junping
>>
>> 
>> From: Junping Du 
>> Sent: Thursday, January 19, 2017 6:46 PM
>> To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>> Cc: Varun Vasudev
>> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>>
>> According to Varun's offline email, the security fixes has landed on
>> branch-2, 2.8 and 2.8.0 branch.
>> I was kicking off a new RC build (RC1), and will publish it for vote
>> soon. In the mean time, please mark fix version as 2.8.1 for any new
>> commits landed on branch-2.8, and don't commit anything to branch-2.8.0 at
>> this moment. Thanks!
>>
>> Cheers,
>>
>> Junping
>>
>> 
>> From: Junping Du 
>> Sent: Wednesday, January 18, 2017 3:26 PM
>> To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
>> Cc: Varun Vasudev
>> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>>
>> Hi folks,
>>  In the passed one or two weeks, we found some new blockers get
>> coming on branch-2.8, like: YARN-6068 (log aggregation get stuck when NM
>> restart with work preserving enabled) and YARN-6072 (RM unable to start in
>> secure mode). Both of them are fixed now (YARN-6072 is fixed by Ajith and I
>> fixed YARN-6068), and I was starting the RC build process since early this
>> week. As we have significant build tools/process change (docker based)
>> since 2.8 comparing with 2.6/2.7, it takes me a while to get familiar with
>> it and finally get a successful build on 2.8.0-RC0 last night.
>>  I already push RC0 tag into public which is prerequisite step before
>> RC voting. However,  in the mean while, I was pinged by Varun Vasudev that
>> there are a known vulnerability issues on container_executor get identified
>> and discussed in hadoop security email threads - looks like YARN-5704 fixed
>> part of it, but left part - the privilege escalation via /proc/self/environ
>> is not fixed yet. So most likely, I have to withdraw our 2.8.0 RC0 although
>> I haven't announced it public for vote yet. I will wait this issue get
>> fixed to prepare a new release candidate. As RC0 tag cannot be reverted
>> after push into apache, our next release candidate will start from RC1.
>> As I mentioned in early email, 2.8.0 is a very big release (2300+
>> commits since 2.7.3) and I am glad that we are almost there. Thanks
>> everyone for being patient and contributing our release work. Please let me
>> know if you have more comments or suggestions.
>>
>&g

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-20 Thread Junping Du

Yes. I did maven deploy in root directory before close the staging repository. 
If this is the only suspect, I can drop the repository and do mvn deploy again.


Thanks,


Junping


From: Andrew Wang 
Sent: Friday, January 20, 2017 10:48 AM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

You can check the error message by clicking on it, a bunch like this:

Missing Signature: 
'/org/apache/hadoop/hadoop-mapreduce-client-jobclient/2.8.0/hadoop-mapreduce-client-jobclient-2.8.0-tests.jar.asc'
 does not exist for 'hadoop-mapreduce-client-jobclient-2.8.0-tests.jar'.

Did you maven deploy all the signature files?

On Fri, Jan 20, 2017 at 2:04 AM, Junping Du 
mailto:j...@hortonworks.com>> wrote:
Hi,
I have successfully built the release bit on branch-2.8.0 by following: 
https://wiki.apache.org/hadoop/HowToRelease step by step. However, when try to 
close the "Staging Repositories" at Nexus page 
(https://repository.apache.org/#stagingRepositories), I found our repository - 
orgapachehadoop-1051 cannot be closed due to some signature validation failed 
and one Apache rule failed. I never met this problem before in previous 
releasing 2.6.3 and 2.6.4. Is this related to our recent changes on release 
process/tools (docker based)? Any ideas or thoughts on how to fix the problem?

Thanks,

Junping


From: Junping Du mailto:j...@hortonworks.com>>
Sent: Thursday, January 19, 2017 6:46 PM
To: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>
Cc: Varun Vasudev
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

According to Varun's offline email, the security fixes has landed on branch-2, 
2.8 and 2.8.0 branch.
I was kicking off a new RC build (RC1), and will publish it for vote soon. In 
the mean time, please mark fix version as 2.8.1 for any new commits landed on 
branch-2.8, and don't commit anything to branch-2.8.0 at this moment. Thanks!

Cheers,

Junping


From: Junping Du mailto:j...@hortonworks.com>>
Sent: Wednesday, January 18, 2017 3:26 PM
To: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>
Cc: Varun Vasudev
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Hi folks,
 In the passed one or two weeks, we found some new blockers get coming on 
branch-2.8, like: YARN-6068 (log aggregation get stuck when NM restart with 
work preserving enabled) and YARN-6072 (RM unable to start in secure mode). 
Both of them are fixed now (YARN-6072 is fixed by Ajith and I fixed YARN-6068), 
and I was starting the RC build process since early this week. As we have 
significant build tools/process change (docker based) since 2.8 comparing with 
2.6/2.7, it takes me a while to get familiar with it and finally get a 
successful build on 2.8.0-RC0 last night.
 I already push RC0 tag into public which is prerequisite step before RC 
voting. However,  in the mean while, I was pinged by Varun Vasudev that there 
are a known vulnerability issues on container_executor get identified and 
discussed in hadoop security email threads - looks like YARN-5704 fixed part of 
it, but left part - the privilege escalation via /proc/self/environ is not 
fixed yet. So most likely, I have to withdraw our 2.8.0 RC0 although I haven't 
announced it public for vote yet. I will wait this issue get fixed to prepare a 
new release candidate. As RC0 tag cannot be reverted after push into apache, 
our next release candidate will start from RC1.
As I mentioned in early email, 2.8.0 is a very big release (2300+ commits 
since 2.7.3) and I am glad that we are almost there. Thanks everyone for being 
patient and contributing our release work. Please let me know if you have more 
comments or suggestions.

Thanks,

Junping

From: Junping Du mailto:j...@hortonworks.com>>
Sent: Wednesday, January 04, 2017 1:41 AM
To: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>
Subject: Re: [Continued] [Release thread] 2.8.0 release activ

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-20 Thread Andrew Wang

You can check the error message by clicking on it, a bunch like this:

Missing Signature:
'/org/apache/hadoop/hadoop-mapreduce-client-jobclient/2.8.0/hadoop-mapreduce-client-jobclient-2.8.0-tests.jar.asc'
does not exist for 'hadoop-mapreduce-client-jobclient-2.8.0-tests.jar'.

Did you maven deploy all the signature files?

On Fri, Jan 20, 2017 at 2:04 AM, Junping Du  wrote:

> Hi,
> I have successfully built the release bit on branch-2.8.0 by
> following: https://wiki.apache.org/hadoop/HowToRelease step by step.
> However, when try to close the "Staging Repositories" at Nexus page (
> https://repository.apache.org/#stagingRepositories), I found our
> repository - orgapachehadoop-1051 cannot be closed due to some signature
> validation failed and one Apache rule failed. I never met this problem
> before in previous releasing 2.6.3 and 2.6.4. Is this related to our recent
> changes on release process/tools (docker based)? Any ideas or thoughts on
> how to fix the problem?
>
> Thanks,
>
> Junping
>
> 
> From: Junping Du 
> Sent: Thursday, January 19, 2017 6:46 PM
> To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> Cc: Varun Vasudev
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> According to Varun's offline email, the security fixes has landed on
> branch-2, 2.8 and 2.8.0 branch.
> I was kicking off a new RC build (RC1), and will publish it for vote soon.
> In the mean time, please mark fix version as 2.8.1 for any new commits
> landed on branch-2.8, and don't commit anything to branch-2.8.0 at this
> moment. Thanks!
>
> Cheers,
>
> Junping
>
> 
> From: Junping Du 
> Sent: Wednesday, January 18, 2017 3:26 PM
> To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> Cc: Varun Vasudev
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> Hi folks,
>  In the passed one or two weeks, we found some new blockers get coming
> on branch-2.8, like: YARN-6068 (log aggregation get stuck when NM restart
> with work preserving enabled) and YARN-6072 (RM unable to start in secure
> mode). Both of them are fixed now (YARN-6072 is fixed by Ajith and I fixed
> YARN-6068), and I was starting the RC build process since early this week.
> As we have significant build tools/process change (docker based) since 2.8
> comparing with 2.6/2.7, it takes me a while to get familiar with it and
> finally get a successful build on 2.8.0-RC0 last night.
>  I already push RC0 tag into public which is prerequisite step before
> RC voting. However,  in the mean while, I was pinged by Varun Vasudev that
> there are a known vulnerability issues on container_executor get identified
> and discussed in hadoop security email threads - looks like YARN-5704 fixed
> part of it, but left part - the privilege escalation via /proc/self/environ
> is not fixed yet. So most likely, I have to withdraw our 2.8.0 RC0 although
> I haven't announced it public for vote yet. I will wait this issue get
> fixed to prepare a new release candidate. As RC0 tag cannot be reverted
> after push into apache, our next release candidate will start from RC1.
> As I mentioned in early email, 2.8.0 is a very big release (2300+
> commits since 2.7.3) and I am glad that we are almost there. Thanks
> everyone for being patient and contributing our release work. Please let me
> know if you have more comments or suggestions.
>
> Thanks,
>
> Junping
> ____________________
> From: Junping Du 
> Sent: Wednesday, January 04, 2017 1:41 AM
> To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> Hi all Hadoopers,
>  I just commit YARN-3866 which is the last blocker for branch-2.8, so
> since tomorrow I will kick off process to prepare the first RC for our
> 2.8.0 release. This release will include at least 2374 commits that never
> landed before in previous 2.x releases. Please check
> https://s.apache.org/RW5k for details. There are also 352 fixes marked in
> 2.7.1, 2.7.2 and 2.7.3 but not marked with 2.8 (https://s.apache.org/RKti)
> that I need to double check all are landed in branch-2.8 and fix the
> versions before kicking off the first RC.
>  Our progress is slightly behind my estimation weeks ago. However,
> considering we just go through holidays and Jenkins cleanup issues linger
> on for several projects (YARN, etc.), our achieveme

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-20 Thread Junping Du

Hi,
I have successfully built the release bit on branch-2.8.0 by following: 
https://wiki.apache.org/hadoop/HowToRelease step by step. However, when try to 
close the "Staging Repositories" at Nexus page 
(https://repository.apache.org/#stagingRepositories), I found our repository - 
orgapachehadoop-1051 cannot be closed due to some signature validation failed 
and one Apache rule failed. I never met this problem before in previous 
releasing 2.6.3 and 2.6.4. Is this related to our recent changes on release 
process/tools (docker based)? Any ideas or thoughts on how to fix the problem?

Thanks,

Junping


From: Junping Du 
Sent: Thursday, January 19, 2017 6:46 PM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Cc: Varun Vasudev
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

According to Varun's offline email, the security fixes has landed on branch-2, 
2.8 and 2.8.0 branch.
I was kicking off a new RC build (RC1), and will publish it for vote soon. In 
the mean time, please mark fix version as 2.8.1 for any new commits landed on 
branch-2.8, and don't commit anything to branch-2.8.0 at this moment. Thanks!

Cheers,

Junping


From: Junping Du 
Sent: Wednesday, January 18, 2017 3:26 PM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Cc: Varun Vasudev
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Hi folks,
 In the passed one or two weeks, we found some new blockers get coming on 
branch-2.8, like: YARN-6068 (log aggregation get stuck when NM restart with 
work preserving enabled) and YARN-6072 (RM unable to start in secure mode). 
Both of them are fixed now (YARN-6072 is fixed by Ajith and I fixed YARN-6068), 
and I was starting the RC build process since early this week. As we have 
significant build tools/process change (docker based) since 2.8 comparing with 
2.6/2.7, it takes me a while to get familiar with it and finally get a 
successful build on 2.8.0-RC0 last night.
 I already push RC0 tag into public which is prerequisite step before RC 
voting. However,  in the mean while, I was pinged by Varun Vasudev that there 
are a known vulnerability issues on container_executor get identified and 
discussed in hadoop security email threads - looks like YARN-5704 fixed part of 
it, but left part - the privilege escalation via /proc/self/environ is not 
fixed yet. So most likely, I have to withdraw our 2.8.0 RC0 although I haven't 
announced it public for vote yet. I will wait this issue get fixed to prepare a 
new release candidate. As RC0 tag cannot be reverted after push into apache, 
our next release candidate will start from RC1.
As I mentioned in early email, 2.8.0 is a very big release (2300+ commits 
since 2.7.3) and I am glad that we are almost there. Thanks everyone for being 
patient and contributing our release work. Please let me know if you have more 
comments or suggestions.

Thanks,

Junping

From: Junping Du 
Sent: Wednesday, January 04, 2017 1:41 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Hi all Hadoopers,
 I just commit YARN-3866 which is the last blocker for branch-2.8, so since 
tomorrow I will kick off process to prepare the first RC for our 2.8.0 release. 
This release will include at least 2374 commits that never landed before in 
previous 2.x releases. Please check https://s.apache.org/RW5k for details. 
There are also 352 fixes marked in 2.7.1, 2.7.2 and 2.7.3 but not marked with 
2.8 (https://s.apache.org/RKti) that I need to double check all are landed in 
branch-2.8 and fix the versions before kicking off the first RC.
 Our progress is slightly behind my estimation weeks ago. However, 
considering we just go through holidays and Jenkins cleanup issues linger on 
for several projects (YARN, etc.), our achievement here is still great! Thanks 
everyone for keep calm and carry on the help for the release. Kudos to Wangda, 
Jian, Akira, Jason, Sangjin, Karthik and all for pushing hard on blockers 
during this time. Also, special thanks to Vinod and Andrew for sharing 
knowledge and practice (include scripts for auto version check) for releasing 
effort.
 Will try to prepare RC0 of 2.8 release for vote within this week. Stay 
tuned!

Thanks,

Junping


From: Junping Du 
Sent: Wednesday, December 07, 2016 11:31 AM
To: Akira Ajisaka; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Akira for reporti

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-19 Thread Junping Du

According to Varun's offline email, the security fixes has landed on branch-2, 
2.8 and 2.8.0 branch. 
I was kicking off a new RC build (RC1), and will publish it for vote soon. In 
the mean time, please mark fix version as 2.8.1 for any new commits landed on 
branch-2.8, and don't commit anything to branch-2.8.0 at this moment. Thanks!

Cheers,

Junping


From: Junping Du 
Sent: Wednesday, January 18, 2017 3:26 PM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Cc: Varun Vasudev
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Hi folks,
 In the passed one or two weeks, we found some new blockers get coming on 
branch-2.8, like: YARN-6068 (log aggregation get stuck when NM restart with 
work preserving enabled) and YARN-6072 (RM unable to start in secure mode). 
Both of them are fixed now (YARN-6072 is fixed by Ajith and I fixed YARN-6068), 
and I was starting the RC build process since early this week. As we have 
significant build tools/process change (docker based) since 2.8 comparing with 
2.6/2.7, it takes me a while to get familiar with it and finally get a 
successful build on 2.8.0-RC0 last night.
 I already push RC0 tag into public which is prerequisite step before RC 
voting. However,  in the mean while, I was pinged by Varun Vasudev that there 
are a known vulnerability issues on container_executor get identified and 
discussed in hadoop security email threads - looks like YARN-5704 fixed part of 
it, but left part - the privilege escalation via /proc/self/environ is not 
fixed yet. So most likely, I have to withdraw our 2.8.0 RC0 although I haven't 
announced it public for vote yet. I will wait this issue get fixed to prepare a 
new release candidate. As RC0 tag cannot be reverted after push into apache, 
our next release candidate will start from RC1.
As I mentioned in early email, 2.8.0 is a very big release (2300+ commits 
since 2.7.3) and I am glad that we are almost there. Thanks everyone for being 
patient and contributing our release work. Please let me know if you have more 
comments or suggestions.

Thanks,

Junping

From: Junping Du 
Sent: Wednesday, January 04, 2017 1:41 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Hi all Hadoopers,
 I just commit YARN-3866 which is the last blocker for branch-2.8, so since 
tomorrow I will kick off process to prepare the first RC for our 2.8.0 release. 
This release will include at least 2374 commits that never landed before in 
previous 2.x releases. Please check https://s.apache.org/RW5k for details. 
There are also 352 fixes marked in 2.7.1, 2.7.2 and 2.7.3 but not marked with 
2.8 (https://s.apache.org/RKti) that I need to double check all are landed in 
branch-2.8 and fix the versions before kicking off the first RC.
 Our progress is slightly behind my estimation weeks ago. However, 
considering we just go through holidays and Jenkins cleanup issues linger on 
for several projects (YARN, etc.), our achievement here is still great! Thanks 
everyone for keep calm and carry on the help for the release. Kudos to Wangda, 
Jian, Akira, Jason, Sangjin, Karthik and all for pushing hard on blockers 
during this time. Also, special thanks to Vinod and Andrew for sharing 
knowledge and practice (include scripts for auto version check) for releasing 
effort.
 Will try to prepare RC0 of 2.8 release for vote within this week. Stay 
tuned!

Thanks,

Junping


From: Junping Du 
Sent: Wednesday, December 07, 2016 11:31 AM
To: Akira Ajisaka; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Akira for reporting this. Actually, HADOOP-2.8-JACC worked well for 
several runs before last weekend, but it get failed for latest several runs, 
probably affected by recently Jenkins down.
However, from my recent manual kick off, it seems to be good again: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/9/. I will 
keep an eye for today's nightly run to see if it back to normal.


Thanks,

Junping


From: Akira Ajisaka 
Sent: Wednesday, December 07, 2016 12:12 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Junping and Andrew!

HADOOP-2.8-JACC is not working well, so I manually kicked a job to
compare 2.8 with 2.7.3.

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-18 Thread Junping Du

Hi folks,
 In the passed one or two weeks, we found some new blockers get coming on 
branch-2.8, like: YARN-6068 (log aggregation get stuck when NM restart with 
work preserving enabled) and YARN-6072 (RM unable to start in secure mode). 
Both of them are fixed now (YARN-6072 is fixed by Ajith and I fixed YARN-6068), 
and I was starting the RC build process since early this week. As we have 
significant build tools/process change (docker based) since 2.8 comparing with 
2.6/2.7, it takes me a while to get familiar with it and finally get a 
successful build on 2.8.0-RC0 last night. 
 I already push RC0 tag into public which is prerequisite step before RC 
voting. However,  in the mean while, I was pinged by Varun Vasudev that there 
are a known vulnerability issues on container_executor get identified and 
discussed in hadoop security email threads - looks like YARN-5704 fixed part of 
it, but left part - the privilege escalation via /proc/self/environ is not 
fixed yet. So most likely, I have to withdraw our 2.8.0 RC0 although I haven't 
announced it public for vote yet. I will wait this issue get fixed to prepare a 
new release candidate. As RC0 tag cannot be reverted after push into apache, 
our next release candidate will start from RC1.
As I mentioned in early email, 2.8.0 is a very big release (2300+ commits 
since 2.7.3) and I am glad that we are almost there. Thanks everyone for being 
patient and contributing our release work. Please let me know if you have more 
comments or suggestions.

Thanks,

Junping

From: Junping Du 
Sent: Wednesday, January 04, 2017 1:41 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Hi all Hadoopers,
 I just commit YARN-3866 which is the last blocker for branch-2.8, so since 
tomorrow I will kick off process to prepare the first RC for our 2.8.0 release. 
This release will include at least 2374 commits that never landed before in 
previous 2.x releases. Please check https://s.apache.org/RW5k for details. 
There are also 352 fixes marked in 2.7.1, 2.7.2 and 2.7.3 but not marked with 
2.8 (https://s.apache.org/RKti) that I need to double check all are landed in 
branch-2.8 and fix the versions before kicking off the first RC.
 Our progress is slightly behind my estimation weeks ago. However, 
considering we just go through holidays and Jenkins cleanup issues linger on 
for several projects (YARN, etc.), our achievement here is still great! Thanks 
everyone for keep calm and carry on the help for the release. Kudos to Wangda, 
Jian, Akira, Jason, Sangjin, Karthik and all for pushing hard on blockers 
during this time. Also, special thanks to Vinod and Andrew for sharing 
knowledge and practice (include scripts for auto version check) for releasing 
effort.
 Will try to prepare RC0 of 2.8 release for vote within this week. Stay 
tuned!

Thanks,

Junping

From: Junping Du 
Sent: Wednesday, December 07, 2016 11:31 AM
To: Akira Ajisaka; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Akira for reporting this. Actually, HADOOP-2.8-JACC worked well for 
several runs before last weekend, but it get failed for latest several runs, 
probably affected by recently Jenkins down.
However, from my recent manual kick off, it seems to be good again: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/9/. I will 
keep an eye for today's nightly run to see if it back to normal.

Thanks,

Junping

From: Akira Ajisaka 
Sent: Wednesday, December 07, 2016 12:12 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Junping and Andrew!

HADOOP-2.8-JACC is not working well, so I manually kicked a job to
compare 2.8 with 2.7.3.

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/report.html

Regards,
Akira

On 2016/12/02 2:08, Junping Du wrote:
> Thanks Andrew! That's also a nice suggestion. I already create a similar job: 
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8 
> and kick off several runs manually. Will monitor incompatible status from 
> there.
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: Andrew Wang 
> Sent: Wednesday, November 30, 2016 4:18 PM
> To: Junping Du
> Cc: Sangjin Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod 
> Vavil

Re: [Continued] [Release thread] 2.8.0 release activities

2017-01-04 Thread Junping Du

Hi all Hadoopers,
 I just commit YARN-3866 which is the last blocker for branch-2.8, so since 
tomorrow I will kick off process to prepare the first RC for our 2.8.0 release. 
This release will include at least 2374 commits that never landed before in 
previous 2.x releases. Please check https://s.apache.org/RW5k for details. 
There are also 352 fixes marked in 2.7.1, 2.7.2 and 2.7.3 but not marked with 
2.8 (https://s.apache.org/RKti) that I need to double check all are landed in 
branch-2.8 and fix the versions before kicking off the first RC.
 Our progress is slightly behind my estimation weeks ago. However, 
considering we just go through holidays and Jenkins cleanup issues linger on 
for several projects (YARN, etc.), our achievement here is still great! Thanks 
everyone for keep calm and carry on the help for the release. Kudos to Wangda, 
Jian, Akira, Jason, Sangjin, Karthik and all for pushing hard on blockers 
during this time. Also, special thanks to Vinod and Andrew for sharing 
knowledge and practice (include scripts for auto version check) for releasing 
effort.
 Will try to prepare RC0 of 2.8 release for vote within this week. Stay 
tuned!

Thanks,

Junping

From: Junping Du 
Sent: Wednesday, December 07, 2016 11:31 AM
To: Akira Ajisaka; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Akira for reporting this. Actually, HADOOP-2.8-JACC worked well for 
several runs before last weekend, but it get failed for latest several runs, 
probably affected by recently Jenkins down.
However, from my recent manual kick off, it seems to be good again: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/9/. I will 
keep an eye for today's nightly run to see if it back to normal.

Thanks,

Junping

From: Akira Ajisaka 
Sent: Wednesday, December 07, 2016 12:12 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Junping and Andrew!

HADOOP-2.8-JACC is not working well, so I manually kicked a job to
compare 2.8 with 2.7.3.

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/report.html

Regards,
Akira

On 2016/12/02 2:08, Junping Du wrote:
> Thanks Andrew! That's also a nice suggestion. I already create a similar job: 
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8 
> and kick off several runs manually. Will monitor incompatible status from 
> there.
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: Andrew Wang 
> Sent: Wednesday, November 30, 2016 4:18 PM
> To: Junping Du
> Cc: Sangjin Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> I recommend giving the JACC report another look. I set up a parameterized 
> jenkins job which you can trigger manually for branch-2.8:
>
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/
>
> On Wed, Nov 30, 2016 at 4:06 PM, Junping Du 
> mailto:j...@hortonworks.com>> wrote:
> Hi Sangjin and all,
>
>  That sounds good. If anyone have priority fix to backport , please 
> nominate it by following this email thread or ping me on JIRA directly. And I 
> agree that we should keep in mind that our bar for 2.8 release should be high 
> now as we want to move quickly on this release. Non-critical fixes can wait 
> for next one.
>
>   Any other comments and suggestions?
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: sjl...@gmail.com<mailto:sjl...@gmail.com> 
> mailto:sjl...@gmail.com>> on behalf of Sangjin Lee 
> mailto:sj...@apache.org>>
> Sent: Wednesday, November 30, 2016 3:24 PM
> To: Junping Du
> Cc: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
> hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
> mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
> yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com<mailto:sj...@twitter.com>
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> Thanks for picking this up Junping!
>
> I heard on email threads and offline discussions that there may be interests 
> in porting some fixe

Re: [Continued] [Release thread] 2.8.0 release activities

2016-12-07 Thread Junping Du

Thanks Akira for reporting this. Actually, HADOOP-2.8-JACC worked well for 
several runs before last weekend, but it get failed for latest several runs, 
probably affected by recently Jenkins down. 
However, from my recent manual kick off, it seems to be good again: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/9/. I will 
keep an eye for today's nightly run to see if it back to normal.


Thanks,

Junping


From: Akira Ajisaka 
Sent: Wednesday, December 07, 2016 12:12 AM
To: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks Junping and Andrew!

HADOOP-2.8-JACC is not working well, so I manually kicked a job to
compare 2.8 with 2.7.3.

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/report.html

Regards,
Akira

On 2016/12/02 2:08, Junping Du wrote:
> Thanks Andrew! That's also a nice suggestion. I already create a similar job: 
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8 
> and kick off several runs manually. Will monitor incompatible status from 
> there.
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: Andrew Wang 
> Sent: Wednesday, November 30, 2016 4:18 PM
> To: Junping Du
> Cc: Sangjin Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> I recommend giving the JACC report another look. I set up a parameterized 
> jenkins job which you can trigger manually for branch-2.8:
>
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/
>
> On Wed, Nov 30, 2016 at 4:06 PM, Junping Du 
> mailto:j...@hortonworks.com>> wrote:
> Hi Sangjin and all,
>
>  That sounds good. If anyone have priority fix to backport , please 
> nominate it by following this email thread or ping me on JIRA directly. And I 
> agree that we should keep in mind that our bar for 2.8 release should be high 
> now as we want to move quickly on this release. Non-critical fixes can wait 
> for next one.
>
>   Any other comments and suggestions?
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: sjl...@gmail.com<mailto:sjl...@gmail.com> 
> mailto:sjl...@gmail.com>> on behalf of Sangjin Lee 
> mailto:sj...@apache.org>>
> Sent: Wednesday, November 30, 2016 3:24 PM
> To: Junping Du
> Cc: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
> hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
> mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
> yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>; Vinod 
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com<mailto:sj...@twitter.com>
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> Thanks for picking this up Junping!
>
> I heard on email threads and offline discussions that there may be interests 
> in porting some fixes from branch-2 to branch-2.8. I still feel that the bar 
> should be pretty high to do that, but it might be good to have folks suggest 
> some critical fixes that need to be released sooner. Thoughts?
>
> On Tue, Nov 29, 2016 at 8:50 PM, Junping Du 
> mailto:j...@hortonworks.com><mailto:j...@hortonworks.com<mailto:j...@hortonworks.com>>>
>  wrote:
> Hi folks,
>  Per asked by Vinod offline, I would like to continue the effort to push 
> 2.8 release out in next several weeks. The plan is as following:
>  - We only have 5 blockers and 3 critical issues 
> (https://s.apache.org/6kwx) so far, and most of them are in good progress 
> now. I put them all on apache ciwiki ( 
> https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release) and 
> will do daily monitor and update on these issues in next couple of weeks.
>  - When all blocker/critical issues are gone (target EOD is Dec. 10), I 
> will push out all major/minor issues that is open. So if you are working on 
> some major issues and target for release in 2.8, please keep track of our 
> release status and your work progress.
>  - I will create RC immediately once our 2.8 target issues are clean 
> (especially for blocker and critical issues) for voting process.
>
>  I hope we can make it within year 2016, best before Xmas holiday. And I 
> need help from all of you. :)
>
>
> Thanks,
>
> Junpin

Re: [Continued] [Release thread] 2.8.0 release activities

2016-12-07 Thread Akira Ajisaka


Thanks Junping and Andrew!

HADOOP-2.8-JACC is not working well, so I manually kicked a job to 
compare 2.8 with 2.7.3.


https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/24/artifact/target/compat-check/report.html

Regards,
Akira

On 2016/12/02 2:08, Junping Du wrote:

Thanks Andrew! That's also a nice suggestion. I already create a similar job: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8 and 
kick off several runs manually. Will monitor incompatible status from there.


Thanks,


Junping



From: Andrew Wang 
Sent: Wednesday, November 30, 2016 4:18 PM
To: Junping Du
Cc: Sangjin Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod Vavilapalli; 
Jian He; Wangda Tan; sj...@twitter.com
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

I recommend giving the JACC report another look. I set up a parameterized 
jenkins job which you can trigger manually for branch-2.8:

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/

On Wed, Nov 30, 2016 at 4:06 PM, Junping Du 
mailto:j...@hortonworks.com>> wrote:
Hi Sangjin and all,

 That sounds good. If anyone have priority fix to backport , please 
nominate it by following this email thread or ping me on JIRA directly. And I 
agree that we should keep in mind that our bar for 2.8 release should be high 
now as we want to move quickly on this release. Non-critical fixes can wait for 
next one.

  Any other comments and suggestions?


Thanks,


Junping



From: sjl...@gmail.com<mailto:sjl...@gmail.com> mailto:sjl...@gmail.com>> 
on behalf of Sangjin Lee mailto:sj...@apache.org>>
Sent: Wednesday, November 30, 2016 3:24 PM
To: Junping Du
Cc: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>; Vinod Vavilapalli; Jian He; Wangda Tan; 
sj...@twitter.com<mailto:sj...@twitter.com>
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks for picking this up Junping!

I heard on email threads and offline discussions that there may be interests in 
porting some fixes from branch-2 to branch-2.8. I still feel that the bar 
should be pretty high to do that, but it might be good to have folks suggest 
some critical fixes that need to be released sooner. Thoughts?

On Tue, Nov 29, 2016 at 8:50 PM, Junping Du 
mailto:j...@hortonworks.com><mailto:j...@hortonworks.com<mailto:j...@hortonworks.com>>>
 wrote:
Hi folks,
 Per asked by Vinod offline, I would like to continue the effort to push 
2.8 release out in next several weeks. The plan is as following:
 - We only have 5 blockers and 3 critical issues 
(https://s.apache.org/6kwx) so far, and most of them are in good progress now. 
I put them all on apache ciwiki ( 
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release) and will 
do daily monitor and update on these issues in next couple of weeks.
 - When all blocker/critical issues are gone (target EOD is Dec. 10), I 
will push out all major/minor issues that is open. So if you are working on 
some major issues and target for release in 2.8, please keep track of our 
release status and your work progress.
 - I will create RC immediately once our 2.8 target issues are clean 
(especially for blocker and critical issues) for voting process.

 I hope we can make it within year 2016, best before Xmas holiday. And I 
need help from all of you. :)


Thanks,

Junping


From: Vinod Kumar Vavilapalli 
mailto:vino...@apache.org><mailto:vino...@apache.org<mailto:vino...@apache.org>>>
Sent: Monday, July 25, 2016 2:57 PM
To: Jian He
Cc: 
mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org><mailto:mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>>;
 yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org><mailto:yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>>; 
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org><mailto:hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>>; 
common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org><mailto:common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>>
Subject: Re: [Release thread] 2.8.0 release activities

Thanks for all that great help moving this release forward, Jian, Sangjin, 
Wangda et al! Appreciate it.

The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last week.

I only see 9 blocker / critical fixes pending for 2.8.0

Re: [Continued] [Release thread] 2.8.0 release activities

2016-12-01 Thread Andrew Wang

One more thing I forgot, there needs to be a bulk fix version update. Vinod
asked me not to update for 2.8.0 when I updated for 3.0.0-alpha1, but
basically there are a lot of JIRAs in 2.6.x and 2.7.x that also need a
2.8.0 fix version so the changelog diffs correctly with 2.7.0.

I posted the scripts I used to do this for 3.0.0-alpha1. You also should
ask infra to disable JIRA updates temporarily while the script runs:

https://github.com/umbrant/versions

Best,
Andrew

On Thu, Dec 1, 2016 at 9:08 AM, Junping Du  wrote:

> Thanks Andrew! That's also a nice suggestion. I already create a similar
> job: https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/
> for 2.8 and kick off several runs manually. Will monitor
> incompatible status from there.
>
>
> Thanks,
>
>
> Junping
>
>
> --
> *From:* Andrew Wang 
> *Sent:* Wednesday, November 30, 2016 4:18 PM
> *To:* Junping Du
> *Cc:* Sangjin Lee; common-...@hadoop.apache.org;
> hdfs-dev@hadoop.apache.org; mapreduce-...@hadoop.apache.org;
> yarn-...@hadoop.apache.org; Vinod Vavilapalli; Jian He; Wangda Tan;
> sj...@twitter.com
>
> *Subject:* Re: [Continued] [Release thread] 2.8.0 release activities
>
> I recommend giving the JACC report another look. I set up a parameterized
> jenkins job which you can trigger manually for branch-2.8:
>
> https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/
>
> On Wed, Nov 30, 2016 at 4:06 PM, Junping Du  wrote:
>
>> Hi Sangjin and all,
>>
>>  That sounds good. If anyone have priority fix to backport , please
>> nominate it by following this email thread or ping me on JIRA directly. And
>> I agree that we should keep in mind that our bar for 2.8 release should be
>> high now as we want to move quickly on this release. Non-critical fixes can
>> wait for next one.
>>
>>   Any other comments and suggestions?
>>
>>
>> Thanks,
>>
>>
>> Junping
>>
>>
>> 
>> From: sjl...@gmail.com  on behalf of Sangjin Lee <
>> sj...@apache.org>
>> Sent: Wednesday, November 30, 2016 3:24 PM
>> To: Junping Du
>> Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
>> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod
>> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
>> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>>
>> Thanks for picking this up Junping!
>>
>> I heard on email threads and offline discussions that there may be
>> interests in porting some fixes from branch-2 to branch-2.8. I still feel
>> that the bar should be pretty high to do that, but it might be good to have
>> folks suggest some critical fixes that need to be released sooner. Thoughts?
>>
>> On Tue, Nov 29, 2016 at 8:50 PM, Junping Du > j...@hortonworks.com>> wrote:
>> Hi folks,
>>  Per asked by Vinod offline, I would like to continue the effort to
>> push 2.8 release out in next several weeks. The plan is as following:
>>  - We only have 5 blockers and 3 critical issues (
>> https://s.apache.org/6kwx) so far, and most of them are in good progress
>> now. I put them all on apache ciwiki ( https://cwiki.apache.org/confl
>> uence/display/HADOOP/Hadoop+2.8+Release) and will do daily monitor and
>> update on these issues in next couple of weeks.
>>  - When all blocker/critical issues are gone (target EOD is Dec. 10),
>> I will push out all major/minor issues that is open. So if you are working
>> on some major issues and target for release in 2.8, please keep track of
>> our release status and your work progress.
>>  - I will create RC immediately once our 2.8 target issues are clean
>> (especially for blocker and critical issues) for voting process.
>>
>>  I hope we can make it within year 2016, best before Xmas holiday.
>> And I need help from all of you. :)
>>
>>
>> Thanks,
>>
>> Junping
>>
>> ________________
>> From: Vinod Kumar Vavilapalli mailto:vin
>> o...@apache.org>>
>> Sent: Monday, July 25, 2016 2:57 PM
>> To: Jian He
>> Cc: mapreduce-...@hadoop.apache.org<mailto:mapreduce-dev@hadoop.
>> apache.org>; yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>;
>> hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>;
>> common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>
>> Subject: Re: [Release thread] 2.8.0 release activities
>>
>> Thanks for all that great help moving this release forward, Jian,
>>

Re: [Continued] [Release thread] 2.8.0 release activities

2016-12-01 Thread Junping Du

Thanks Andrew! That's also a nice suggestion. I already create a similar job: 
https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-2.8-JACC/ for 2.8 and 
kick off several runs manually. Will monitor incompatible status from there.

Thanks,

Junping

From: Andrew Wang 
Sent: Wednesday, November 30, 2016 4:18 PM
To: Junping Du
Cc: Sangjin Lee; common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod Vavilapalli; 
Jian He; Wangda Tan; sj...@twitter.com
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

I recommend giving the JACC report another look. I set up a parameterized 
jenkins job which you can trigger manually for branch-2.8:

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/

On Wed, Nov 30, 2016 at 4:06 PM, Junping Du 
mailto:j...@hortonworks.com>> wrote:
Hi Sangjin and all,

 That sounds good. If anyone have priority fix to backport , please 
nominate it by following this email thread or ping me on JIRA directly. And I 
agree that we should keep in mind that our bar for 2.8 release should be high 
now as we want to move quickly on this release. Non-critical fixes can wait for 
next one.

  Any other comments and suggestions?

Thanks,

Junping

From: sjl...@gmail.com<mailto:sjl...@gmail.com> 
mailto:sjl...@gmail.com>> on behalf of Sangjin Lee 
mailto:sj...@apache.org>>
Sent: Wednesday, November 30, 2016 3:24 PM
To: Junping Du
Cc: common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>; 
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>; Vinod 
Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com<mailto:sj...@twitter.com>
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks for picking this up Junping!

I heard on email threads and offline discussions that there may be interests in 
porting some fixes from branch-2 to branch-2.8. I still feel that the bar 
should be pretty high to do that, but it might be good to have folks suggest 
some critical fixes that need to be released sooner. Thoughts?

On Tue, Nov 29, 2016 at 8:50 PM, Junping Du 
mailto:j...@hortonworks.com><mailto:j...@hortonworks.com<mailto:j...@hortonworks.com>>>
 wrote:
Hi folks,
 Per asked by Vinod offline, I would like to continue the effort to push 
2.8 release out in next several weeks. The plan is as following:
 - We only have 5 blockers and 3 critical issues 
(https://s.apache.org/6kwx) so far, and most of them are in good progress now. 
I put them all on apache ciwiki ( 
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release) and will 
do daily monitor and update on these issues in next couple of weeks.
 - When all blocker/critical issues are gone (target EOD is Dec. 10), I 
will push out all major/minor issues that is open. So if you are working on 
some major issues and target for release in 2.8, please keep track of our 
release status and your work progress.
 - I will create RC immediately once our 2.8 target issues are clean 
(especially for blocker and critical issues) for voting process.

 I hope we can make it within year 2016, best before Xmas holiday. And I 
need help from all of you. :)

Thanks,

Junping

From: Vinod Kumar Vavilapalli 
mailto:vino...@apache.org><mailto:vino...@apache.org<mailto:vino...@apache.org>>>
Sent: Monday, July 25, 2016 2:57 PM
To: Jian He
Cc: 
mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org><mailto:mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>>;

yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org><mailto:yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>>;

hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org><mailto:hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>>;

common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org><mailto:common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>>
Subject: Re: [Release thread] 2.8.0 release activities

Thanks for all that great help moving this release forward, Jian, Sangjin, 
Wangda et al! Appreciate it.

The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last week.

I only see 9 blocker / critical fixes pending for 2.8.0 - 
https://issues.apache.org/jira/issues/?filter=12334985. Let’s do this!

Thanks
+Vinod

> On May 11, 2016, at 6:04 PM, Jian He 
> mailto:j...@hortonworks.com><mailto:j...@hortonworks.com<mailto:j...@hortonworks.com>>>
>  wrote:
>
> For MapReduce/YARN, I closed a few

Re: [Continued] [Release thread] 2.8.0 release activities

2016-11-30 Thread Andrew Wang

I recommend giving the JACC report another look. I set up a parameterized
jenkins job which you can trigger manually for branch-2.8:

https://builds.apache.org/view/H-L/view/Hadoop/job/Hadoop-trunk-JACC/

On Wed, Nov 30, 2016 at 4:06 PM, Junping Du  wrote:

> Hi Sangjin and all,
>
>  That sounds good. If anyone have priority fix to backport , please
> nominate it by following this email thread or ping me on JIRA directly. And
> I agree that we should keep in mind that our bar for 2.8 release should be
> high now as we want to move quickly on this release. Non-critical fixes can
> wait for next one.
>
>   Any other comments and suggestions?
>
>
> Thanks,
>
>
> Junping
>
>
> 
> From: sjl...@gmail.com  on behalf of Sangjin Lee <
> sj...@apache.org>
> Sent: Wednesday, November 30, 2016 3:24 PM
> To: Junping Du
> Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org;
> mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> Thanks for picking this up Junping!
>
> I heard on email threads and offline discussions that there may be
> interests in porting some fixes from branch-2 to branch-2.8. I still feel
> that the bar should be pretty high to do that, but it might be good to have
> folks suggest some critical fixes that need to be released sooner. Thoughts?
>
> On Tue, Nov 29, 2016 at 8:50 PM, Junping Du mailto:jd
> u...@hortonworks.com>> wrote:
> Hi folks,
>  Per asked by Vinod offline, I would like to continue the effort to
> push 2.8 release out in next several weeks. The plan is as following:
>  - We only have 5 blockers and 3 critical issues (
> https://s.apache.org/6kwx) so far, and most of them are in good progress
> now. I put them all on apache ciwiki ( https://cwiki.apache.org/
> confluence/display/HADOOP/Hadoop+2.8+Release) and will do daily monitor
> and update on these issues in next couple of weeks.
>  - When all blocker/critical issues are gone (target EOD is Dec. 10),
> I will push out all major/minor issues that is open. So if you are working
> on some major issues and target for release in 2.8, please keep track of
> our release status and your work progress.
>  - I will create RC immediately once our 2.8 target issues are clean
> (especially for blocker and critical issues) for voting process.
>
>  I hope we can make it within year 2016, best before Xmas holiday. And
> I need help from all of you. :)
>
>
> Thanks,
>
> Junping
>
> 
> From: Vinod Kumar Vavilapalli mailto:vin
> o...@apache.org>>
> Sent: Monday, July 25, 2016 2:57 PM
> To: Jian He
> Cc: mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>;
> yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>;
> hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>;
> common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>
> Subject: Re: [Release thread] 2.8.0 release activities
>
> Thanks for all that great help moving this release forward, Jian, Sangjin,
> Wangda et al! Appreciate it.
>
> The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last
> week.
>
> I only see 9 blocker / critical fixes pending for 2.8.0 -
> https://issues.apache.org/jira/issues/?filter=12334985. Let’s do this!
>
> Thanks
> +Vinod
>
> > On May 11, 2016, at 6:04 PM, Jian He mailto:jh
> e...@hortonworks.com>> wrote:
> >
> > For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs
> attention for 2.8
> >
> > MAPREDUCE-6288
> > YARN-1815
> > YARN-4685
> > YARN-4844
> >
> > The rest are either improvements or long-standing issues and does not
> qualify release blocker, IMO.
> > I think we’ll try to get these 4 jiras in asap. The rest will be on best
> effort, resolve as much as possible and move them out if not resolved in
> time.
> >
> > Jian
> >
> > On May 11, 2016, at 5:37 PM, Wangda Tan mailto:wh
> eele...@gmail.com><mailto:wheele...@gmail.com<mailto:wheele...@gmail.com>>>
> wrote:
> >
> > Sounds good to me :).
> >
> > Jian and I have looked at all existing 2.8.0 blockers and criticals
> today.
> > To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
> > out. Left comments on these JIRAs asked original owners, plan to update
> > target version of these JIRAs early next week.
> >
> > Will keep this thread updated.
> >
> > Thanks,
> > Wangda
>

Re: [Continued] [Release thread] 2.8.0 release activities

2016-11-30 Thread Junping Du

Hi Sangjin and all,

 That sounds good. If anyone have priority fix to backport , please 
nominate it by following this email thread or ping me on JIRA directly. And I 
agree that we should keep in mind that our bar for 2.8 release should be high 
now as we want to move quickly on this release. Non-critical fixes can wait for 
next one.

  Any other comments and suggestions?


Thanks,


Junping



From: sjl...@gmail.com  on behalf of Sangjin Lee 

Sent: Wednesday, November 30, 2016 3:24 PM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-dev@hadoop.apache.org; 
mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod Vavilapalli; 
Jian He; Wangda Tan; sj...@twitter.com
Subject: Re: [Continued] [Release thread] 2.8.0 release activities

Thanks for picking this up Junping!

I heard on email threads and offline discussions that there may be interests in 
porting some fixes from branch-2 to branch-2.8. I still feel that the bar 
should be pretty high to do that, but it might be good to have folks suggest 
some critical fixes that need to be released sooner. Thoughts?

On Tue, Nov 29, 2016 at 8:50 PM, Junping Du 
mailto:j...@hortonworks.com>> wrote:
Hi folks,
 Per asked by Vinod offline, I would like to continue the effort to push 
2.8 release out in next several weeks. The plan is as following:
 - We only have 5 blockers and 3 critical issues 
(https://s.apache.org/6kwx) so far, and most of them are in good progress now. 
I put them all on apache ciwiki ( 
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release) and will 
do daily monitor and update on these issues in next couple of weeks.
 - When all blocker/critical issues are gone (target EOD is Dec. 10), I 
will push out all major/minor issues that is open. So if you are working on 
some major issues and target for release in 2.8, please keep track of our 
release status and your work progress.
 - I will create RC immediately once our 2.8 target issues are clean 
(especially for blocker and critical issues) for voting process.

 I hope we can make it within year 2016, best before Xmas holiday. And I 
need help from all of you. :)


Thanks,

Junping


From: Vinod Kumar Vavilapalli mailto:vino...@apache.org>>
Sent: Monday, July 25, 2016 2:57 PM
To: Jian He
Cc: mapreduce-...@hadoop.apache.org<mailto:mapreduce-...@hadoop.apache.org>; 
yarn-...@hadoop.apache.org<mailto:yarn-...@hadoop.apache.org>; 
hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>; 
common-...@hadoop.apache.org<mailto:common-...@hadoop.apache.org>
Subject: Re: [Release thread] 2.8.0 release activities

Thanks for all that great help moving this release forward, Jian, Sangjin, 
Wangda et al! Appreciate it.

The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last week.

I only see 9 blocker / critical fixes pending for 2.8.0 - 
https://issues.apache.org/jira/issues/?filter=12334985. Let’s do this!

Thanks
+Vinod

> On May 11, 2016, at 6:04 PM, Jian He 
> mailto:j...@hortonworks.com>> wrote:
>
> For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs attention 
> for 2.8
>
> MAPREDUCE-6288
> YARN-1815
> YARN-4685
> YARN-4844
>
> The rest are either improvements or long-standing issues and does not qualify 
> release blocker, IMO.
> I think we’ll try to get these 4 jiras in asap. The rest will be on best 
> effort, resolve as much as possible and move them out if not resolved in time.
>
> Jian
>
> On May 11, 2016, at 5:37 PM, Wangda Tan 
> mailto:wheele...@gmail.com><mailto:wheele...@gmail.com<mailto:wheele...@gmail.com>>>
>  wrote:
>
> Sounds good to me :).
>
> Jian and I have looked at all existing 2.8.0 blockers and criticals today.
> To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
> out. Left comments on these JIRAs asked original owners, plan to update
> target version of these JIRAs early next week.
>
> Will keep this thread updated.
>
> Thanks,
> Wangda
>
>
> On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee 
> mailto:sj...@apache.org><mailto:sj...@apache.org<mailto:sj...@apache.org>>>
>  wrote:
>
> How about this? I'll review the HADOOP/HDFS bugs in that list to come up
> with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
> report the list here. Then folks can chime in if you agree
>
> Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
>
> Thanks,
> Sangjin
>
> On Wed, May 11, 2016 at 4:26 PM, Wangda Tan 
> mailto:wheele...@gmail.com><mailto:wheele...@gmail.com<mailto:wheele...@gmail.com>>>
>  wrote:
>
> +1, we should close such staled JIRAs to avoid doing unnecessary checks
> for
> every releas

Re: [Continued] [Release thread] 2.8.0 release activities

2016-11-30 Thread Sangjin Lee

Thanks for picking this up Junping!

I heard on email threads and offline discussions that there may be
interests in porting some fixes from branch-2 to branch-2.8. I still feel
that the bar should be pretty high to do that, but it might be good to have
folks suggest some critical fixes that need to be released sooner. Thoughts?

On Tue, Nov 29, 2016 at 8:50 PM, Junping Du  wrote:

> Hi folks,
>  Per asked by Vinod offline, I would like to continue the effort to
> push 2.8 release out in next several weeks. The plan is as following:
>  - We only have 5 blockers and 3 critical issues (
> https://s.apache.org/6kwx) so far, and most of them are in good progress
> now. I put them all on apache ciwiki ( https://cwiki.apache.org/
> confluence/display/HADOOP/Hadoop+2.8+Release) and will do daily monitor
> and update on these issues in next couple of weeks.
>  - When all blocker/critical issues are gone (target EOD is Dec. 10),
> I will push out all major/minor issues that is open. So if you are working
> on some major issues and target for release in 2.8, please keep track of
> our release status and your work progress.
>  - I will create RC immediately once our 2.8 target issues are clean
> (especially for blocker and critical issues) for voting process.
>
>  I hope we can make it within year 2016, best before Xmas holiday. And
> I need help from all of you. :)
>
>
> Thanks,
>
> Junping
>
> 
> From: Vinod Kumar Vavilapalli 
> Sent: Monday, July 25, 2016 2:57 PM
> To: Jian He
> Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org;
> hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
> Subject: Re: [Release thread] 2.8.0 release activities
>
> Thanks for all that great help moving this release forward, Jian, Sangjin,
> Wangda et al! Appreciate it.
>
> The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last
> week.
>
> I only see 9 blocker / critical fixes pending for 2.8.0 -
> https://issues.apache.org/jira/issues/?filter=12334985. Let’s do this!
>
> Thanks
> +Vinod
>
> > On May 11, 2016, at 6:04 PM, Jian He  wrote:
> >
> > For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs
> attention for 2.8
> >
> > MAPREDUCE-6288
> > YARN-1815
> > YARN-4685
> > YARN-4844
> >
> > The rest are either improvements or long-standing issues and does not
> qualify release blocker, IMO.
> > I think we’ll try to get these 4 jiras in asap. The rest will be on best
> effort, resolve as much as possible and move them out if not resolved in
> time.
> >
> > Jian
> >
> > On May 11, 2016, at 5:37 PM, Wangda Tan mailto:wh
> eele...@gmail.com>> wrote:
> >
> > Sounds good to me :).
> >
> > Jian and I have looked at all existing 2.8.0 blockers and criticals
> today.
> > To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
> > out. Left comments on these JIRAs asked original owners, plan to update
> > target version of these JIRAs early next week.
> >
> > Will keep this thread updated.
> >
> > Thanks,
> > Wangda
> >
> >
> > On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee  sj...@apache.org>> wrote:
> >
> > How about this? I'll review the HADOOP/HDFS bugs in that list to come up
> > with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
> > report the list here. Then folks can chime in if you agree
> >
> > Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
> >
> > Thanks,
> > Sangjin
> >
> > On Wed, May 11, 2016 at 4:26 PM, Wangda Tan  wheele...@gmail.com>> wrote:
> >
> > +1, we should close such staled JIRAs to avoid doing unnecessary checks
> > for
> > every releases.
> >
> > I'm working on reviewing YARN/MR critical/blocker patches currently, it
> > gonna very helpful if someone else can help with reviewing Common/HDFS
> > JIRAs.
> >
> > Thanks,
> > Wangda
> >
> >
> > On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee  sj...@apache.org>> wrote:
> >
> > Where do we stand in terms of closing out blocker/critical issues for
> > 2.8.0? I still see 50 open JIRAs in Vinod's list:
> > https://issues.apache.org/jira/issues/?filter=12334985
> >
> > But I see a lot of JIRAs with no patches or very stale patches. It
> > would be
> > a good exercise to come up with the list of JIRAs that we need to block
> > 2.8.0 for and focus our attention on closing them out. Thoughts?
> >
> > Thanks,
> > Sangjin
> >
> >

[Continued] [Release thread] 2.8.0 release activities

2016-11-29 Thread Junping Du

Hi folks,
 Per asked by Vinod offline, I would like to continue the effort to push 
2.8 release out in next several weeks. The plan is as following:
 - We only have 5 blockers and 3 critical issues 
(https://s.apache.org/6kwx) so far, and most of them are in good progress now. 
I put them all on apache ciwiki ( 
https://cwiki.apache.org/confluence/display/HADOOP/Hadoop+2.8+Release) and will 
do daily monitor and update on these issues in next couple of weeks.
 - When all blocker/critical issues are gone (target EOD is Dec. 10), I 
will push out all major/minor issues that is open. So if you are working on 
some major issues and target for release in 2.8, please keep track of our 
release status and your work progress.
 - I will create RC immediately once our 2.8 target issues are clean 
(especially for blocker and critical issues) for voting process. 

 I hope we can make it within year 2016, best before Xmas holiday. And I 
need help from all of you. :)


Thanks,

Junping


From: Vinod Kumar Vavilapalli 
Sent: Monday, July 25, 2016 2:57 PM
To: Jian He
Cc: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; 
hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
Subject: Re: [Release thread] 2.8.0 release activities

Thanks for all that great help moving this release forward, Jian, Sangjin, 
Wangda et al! Appreciate it.

The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last week.

I only see 9 blocker / critical fixes pending for 2.8.0 - 
https://issues.apache.org/jira/issues/?filter=12334985. Let’s do this!

Thanks
+Vinod

> On May 11, 2016, at 6:04 PM, Jian He  wrote:
>
> For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs attention 
> for 2.8
>
> MAPREDUCE-6288
> YARN-1815
> YARN-4685
> YARN-4844
>
> The rest are either improvements or long-standing issues and does not qualify 
> release blocker, IMO.
> I think we’ll try to get these 4 jiras in asap. The rest will be on best 
> effort, resolve as much as possible and move them out if not resolved in time.
>
> Jian
>
> On May 11, 2016, at 5:37 PM, Wangda Tan 
> mailto:wheele...@gmail.com>> wrote:
>
> Sounds good to me :).
>
> Jian and I have looked at all existing 2.8.0 blockers and criticals today.
> To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
> out. Left comments on these JIRAs asked original owners, plan to update
> target version of these JIRAs early next week.
>
> Will keep this thread updated.
>
> Thanks,
> Wangda
>
>
> On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee 
> mailto:sj...@apache.org>> wrote:
>
> How about this? I'll review the HADOOP/HDFS bugs in that list to come up
> with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
> report the list here. Then folks can chime in if you agree
>
> Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
>
> Thanks,
> Sangjin
>
> On Wed, May 11, 2016 at 4:26 PM, Wangda Tan 
> mailto:wheele...@gmail.com>> wrote:
>
> +1, we should close such staled JIRAs to avoid doing unnecessary checks
> for
> every releases.
>
> I'm working on reviewing YARN/MR critical/blocker patches currently, it
> gonna very helpful if someone else can help with reviewing Common/HDFS
> JIRAs.
>
> Thanks,
> Wangda
>
>
> On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee 
> mailto:sj...@apache.org>> wrote:
>
> Where do we stand in terms of closing out blocker/critical issues for
> 2.8.0? I still see 50 open JIRAs in Vinod's list:
> https://issues.apache.org/jira/issues/?filter=12334985
>
> But I see a lot of JIRAs with no patches or very stale patches. It
> would be
> a good exercise to come up with the list of JIRAs that we need to block
> 2.8.0 for and focus our attention on closing them out. Thoughts?
>
> Thanks,
> Sangjin
>
> On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran 
> mailto:ste...@hortonworks.com>
>
> wrote:
>
>
> On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli <
> vino...@apache.org<mailto:vino...@apache.org>>
> wrote:
>
> We are not converging - there’s still 58 more. I need help from the
> community in addressing / review 2.8.0 blockers. If folks can start
> with
> reviewing Patch available tickets, that’ll be great.
>
>
>
>
> I'm still doing the s3a stuff, other people testing and reviewing this
> stuff welcome.
>
> in particular, I could do with others playing with this patch of mine,
> which adds counters and things into S3a, based on the azure
> instrumentation
>
> https://issues.apache.org/jira/browse/HADOOP-13028
>
>
>
>
>
>
>
>


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


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

Re: [Release thread] 2.8.0 release activities

2016-07-25 Thread Vinod Kumar Vavilapalli

Thanks for all that great help moving this release forward, Jian, Sangjin, 
Wangda et al! Appreciate it.

The License / Notice fix is finally in. And I pushed out a 2.7.3 RC0 last week.

I only see 9 blocker / critical fixes pending for 2.8.0 - 
https://issues.apache.org/jira/issues/?filter=12334985. Let’s do this!

Thanks
+Vinod

> On May 11, 2016, at 6:04 PM, Jian He  wrote:
> 
> For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs attention 
> for 2.8
> 
> MAPREDUCE-6288
> YARN-1815
> YARN-4685
> YARN-4844
> 
> The rest are either improvements or long-standing issues and does not qualify 
> release blocker, IMO.
> I think we’ll try to get these 4 jiras in asap. The rest will be on best 
> effort, resolve as much as possible and move them out if not resolved in time.
> 
> Jian
> 
> On May 11, 2016, at 5:37 PM, Wangda Tan 
> mailto:wheele...@gmail.com>> wrote:
> 
> Sounds good to me :).
> 
> Jian and I have looked at all existing 2.8.0 blockers and criticals today.
> To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
> out. Left comments on these JIRAs asked original owners, plan to update
> target version of these JIRAs early next week.
> 
> Will keep this thread updated.
> 
> Thanks,
> Wangda
> 
> 
> On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee 
> mailto:sj...@apache.org>> wrote:
> 
> How about this? I'll review the HADOOP/HDFS bugs in that list to come up
> with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
> report the list here. Then folks can chime in if you agree
> 
> Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
> 
> Thanks,
> Sangjin
> 
> On Wed, May 11, 2016 at 4:26 PM, Wangda Tan 
> mailto:wheele...@gmail.com>> wrote:
> 
> +1, we should close such staled JIRAs to avoid doing unnecessary checks
> for
> every releases.
> 
> I'm working on reviewing YARN/MR critical/blocker patches currently, it
> gonna very helpful if someone else can help with reviewing Common/HDFS
> JIRAs.
> 
> Thanks,
> Wangda
> 
> 
> On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee 
> mailto:sj...@apache.org>> wrote:
> 
> Where do we stand in terms of closing out blocker/critical issues for
> 2.8.0? I still see 50 open JIRAs in Vinod's list:
> https://issues.apache.org/jira/issues/?filter=12334985
> 
> But I see a lot of JIRAs with no patches or very stale patches. It
> would be
> a good exercise to come up with the list of JIRAs that we need to block
> 2.8.0 for and focus our attention on closing them out. Thoughts?
> 
> Thanks,
> Sangjin
> 
> On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran 
> mailto:ste...@hortonworks.com>
> 
> wrote:
> 
> 
> On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli <
> vino...@apache.org>
> wrote:
> 
> We are not converging - there’s still 58 more. I need help from the
> community in addressing / review 2.8.0 blockers. If folks can start
> with
> reviewing Patch available tickets, that’ll be great.
> 
> 
> 
> 
> I'm still doing the s3a stuff, other people testing and reviewing this
> stuff welcome.
> 
> in particular, I could do with others playing with this patch of mine,
> which adds counters and things into S3a, based on the azure
> instrumentation
> 
> https://issues.apache.org/jira/browse/HADOOP-13028
> 
> 
> 
> 
> 
> 
> 
> 


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

RE: [Release thread] 2.8.0 release activities

2016-05-19 Thread Rohith Sharma K S

There are few test cases regularly failing in YARN because of 
HADOOP-12687(issue with DNS). This issue is blocker for releases since YARN 
test cases do not guarantee quality. 

There are some patches ready for this issue. But we doubt will this violate 
RFC-1535? 

I would like to hear opinion from community on this.


Thanks & Regards
Rohith Sharma K S

-Original Message-
From: Jian He [mailto:j...@hortonworks.com] 
Sent: 12 May 2016 06:34
To: mapreduce-...@hadoop.apache.org; yarn-...@hadoop.apache.org; 
hdfs-dev@hadoop.apache.org; common-...@hadoop.apache.org
Subject: Re: [Release thread] 2.8.0 release activities

For MapReduce/YARN, I closed a few staled ones. Only 4 jiras needs attention 
for 2.8

MAPREDUCE-6288
YARN-1815
YARN-4685
YARN-4844

The rest are either improvements or long-standing issues and does not qualify 
release blocker, IMO.
I think we’ll try to get these 4 jiras in asap. The rest will be on best 
effort, resolve as much as possible and move them out if not resolved in time.

Jian

On May 11, 2016, at 5:37 PM, Wangda Tan 
mailto:wheele...@gmail.com>> wrote:

Sounds good to me :).

Jian and I have looked at all existing 2.8.0 blockers and criticals today.
To me more than half of MR/YARN blockers/criticals of 2.8 should be moved out. 
Left comments on these JIRAs asked original owners, plan to update target 
version of these JIRAs early next week.

Will keep this thread updated.

Thanks,
Wangda


On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee 
mailto:sj...@apache.org>> wrote:

How about this? I'll review the HADOOP/HDFS bugs in that list to come up with 
true blockers for 2.8.0 or JIRAs that are close to being ready. I'll report the 
list here. Then folks can chime in if you agree

Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?

Thanks,
Sangjin

On Wed, May 11, 2016 at 4:26 PM, Wangda Tan 
mailto:wheele...@gmail.com>> wrote:

+1, we should close such staled JIRAs to avoid doing unnecessary checks
for
every releases.

I'm working on reviewing YARN/MR critical/blocker patches currently, it gonna 
very helpful if someone else can help with reviewing Common/HDFS JIRAs.

Thanks,
Wangda


On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee 
mailto:sj...@apache.org>> wrote:

Where do we stand in terms of closing out blocker/critical issues for 2.8.0? I 
still see 50 open JIRAs in Vinod's list:
https://issues.apache.org/jira/issues/?filter=12334985

But I see a lot of JIRAs with no patches or very stale patches. It would be a 
good exercise to come up with the list of JIRAs that we need to block
2.8.0 for and focus our attention on closing them out. Thoughts?

Thanks,
Sangjin

On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran 
mailto:ste...@hortonworks.com>

wrote:


On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli < 
vino...@apache.org<mailto:vino...@apache.org>>
wrote:

We are not converging - there’s still 58 more. I need help from the community 
in addressing / review 2.8.0 blockers. If folks can start with reviewing Patch 
available tickets, that’ll be great.




I'm still doing the s3a stuff, other people testing and reviewing this stuff 
welcome.

in particular, I could do with others playing with this patch of mine, which 
adds counters and things into S3a, based on the azure instrumentation

https://issues.apache.org/jira/browse/HADOOP-13028









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

Re: [Release thread] 2.8.0 release activities

2016-05-11 Thread Sangjin Lee

I see the following list of JIRAs from HADOOP and HDFS as blockers for
2.8.0. Other JIRAs are either old issues with little movement or new issues
that don't appear to be as critical/ready.

- HADOOP-12893
- HADOOP-12892
- HADOOP-10940 (patch ready?)
- HADOOP-12971 (can be done relatively quickly?)
- HDFS-7959
- HDFS-7597 (needs review/some more work?)

I would propose moving the rest out of scope for 2.8.0 (23 JIRAs). Let me
know what you think.


On Wed, May 11, 2016 at 5:37 PM, Wangda Tan  wrote:

> Sounds good to me :).
>
> Jian and I have looked at all existing 2.8.0 blockers and criticals today.
> To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
> out. Left comments on these JIRAs asked original owners, plan to update
> target version of these JIRAs early next week.
>
> Will keep this thread updated.
>
> Thanks,
> Wangda
>
>
> On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee  wrote:
>
>> How about this? I'll review the HADOOP/HDFS bugs in that list to come up
>> with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
>> report the list here. Then folks can chime in if you agree
>>
>> Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
>>
>> Thanks,
>> Sangjin
>>
>> On Wed, May 11, 2016 at 4:26 PM, Wangda Tan  wrote:
>>
>>> +1, we should close such staled JIRAs to avoid doing unnecessary checks
>>> for
>>> every releases.
>>>
>>> I'm working on reviewing YARN/MR critical/blocker patches currently, it
>>> gonna very helpful if someone else can help with reviewing Common/HDFS
>>> JIRAs.
>>>
>>> Thanks,
>>> Wangda
>>>
>>>
>>> On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee  wrote:
>>>
>>> > Where do we stand in terms of closing out blocker/critical issues for
>>> > 2.8.0? I still see 50 open JIRAs in Vinod's list:
>>> > https://issues.apache.org/jira/issues/?filter=12334985
>>> >
>>> > But I see a lot of JIRAs with no patches or very stale patches. It
>>> would be
>>> > a good exercise to come up with the list of JIRAs that we need to block
>>> > 2.8.0 for and focus our attention on closing them out. Thoughts?
>>> >
>>> > Thanks,
>>> > Sangjin
>>> >
>>> > On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran <
>>> ste...@hortonworks.com>
>>> > wrote:
>>> >
>>> > >
>>> > > > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli <
>>> vino...@apache.org>
>>> > > wrote:
>>> > > >
>>> > > > We are not converging - there’s still 58 more. I need help from the
>>> > > community in addressing / review 2.8.0 blockers. If folks can start
>>> with
>>> > > reviewing Patch available tickets, that’ll be great.
>>> > > >
>>> > > >
>>> > >
>>> > >
>>> > > I'm still doing the s3a stuff, other people testing and reviewing
>>> this
>>> > > stuff welcome.
>>> > >
>>> > > in particular, I could do with others playing with this patch of
>>> mine,
>>> > > which adds counters and things into S3a, based on the azure
>>> > instrumentation
>>> > >
>>> > > https://issues.apache.org/jira/browse/HADOOP-13028
>>> > >
>>> > >
>>> > >
>>> >
>>>
>>
>>
>

Re: [Release thread] 2.8.0 release activities

2016-05-11 Thread Wangda Tan

Sounds good to me :).

Jian and I have looked at all existing 2.8.0 blockers and criticals today.
To me more than half of MR/YARN blockers/criticals of 2.8 should be moved
out. Left comments on these JIRAs asked original owners, plan to update
target version of these JIRAs early next week.

Will keep this thread updated.

Thanks,
Wangda


On Wed, May 11, 2016 at 5:06 PM, Sangjin Lee  wrote:

> How about this? I'll review the HADOOP/HDFS bugs in that list to come up
> with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
> report the list here. Then folks can chime in if you agree
>
> Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?
>
> Thanks,
> Sangjin
>
> On Wed, May 11, 2016 at 4:26 PM, Wangda Tan  wrote:
>
>> +1, we should close such staled JIRAs to avoid doing unnecessary checks
>> for
>> every releases.
>>
>> I'm working on reviewing YARN/MR critical/blocker patches currently, it
>> gonna very helpful if someone else can help with reviewing Common/HDFS
>> JIRAs.
>>
>> Thanks,
>> Wangda
>>
>>
>> On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee  wrote:
>>
>> > Where do we stand in terms of closing out blocker/critical issues for
>> > 2.8.0? I still see 50 open JIRAs in Vinod's list:
>> > https://issues.apache.org/jira/issues/?filter=12334985
>> >
>> > But I see a lot of JIRAs with no patches or very stale patches. It
>> would be
>> > a good exercise to come up with the list of JIRAs that we need to block
>> > 2.8.0 for and focus our attention on closing them out. Thoughts?
>> >
>> > Thanks,
>> > Sangjin
>> >
>> > On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran > >
>> > wrote:
>> >
>> > >
>> > > > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli <
>> vino...@apache.org>
>> > > wrote:
>> > > >
>> > > > We are not converging - there’s still 58 more. I need help from the
>> > > community in addressing / review 2.8.0 blockers. If folks can start
>> with
>> > > reviewing Patch available tickets, that’ll be great.
>> > > >
>> > > >
>> > >
>> > >
>> > > I'm still doing the s3a stuff, other people testing and reviewing this
>> > > stuff welcome.
>> > >
>> > > in particular, I could do with others playing with this patch of mine,
>> > > which adds counters and things into S3a, based on the azure
>> > instrumentation
>> > >
>> > > https://issues.apache.org/jira/browse/HADOOP-13028
>> > >
>> > >
>> > >
>> >
>>
>
>

Re: [Release thread] 2.8.0 release activities

2016-05-11 Thread Sangjin Lee

How about this? I'll review the HADOOP/HDFS bugs in that list to come up
with true blockers for 2.8.0 or JIRAs that are close to being ready. I'll
report the list here. Then folks can chime in if you agree

Perhaps Wangda, you can go over the YARN/MR bugs. Sound like a plan?

Thanks,
Sangjin

On Wed, May 11, 2016 at 4:26 PM, Wangda Tan  wrote:

> +1, we should close such staled JIRAs to avoid doing unnecessary checks for
> every releases.
>
> I'm working on reviewing YARN/MR critical/blocker patches currently, it
> gonna very helpful if someone else can help with reviewing Common/HDFS
> JIRAs.
>
> Thanks,
> Wangda
>
>
> On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee  wrote:
>
> > Where do we stand in terms of closing out blocker/critical issues for
> > 2.8.0? I still see 50 open JIRAs in Vinod's list:
> > https://issues.apache.org/jira/issues/?filter=12334985
> >
> > But I see a lot of JIRAs with no patches or very stale patches. It would
> be
> > a good exercise to come up with the list of JIRAs that we need to block
> > 2.8.0 for and focus our attention on closing them out. Thoughts?
> >
> > Thanks,
> > Sangjin
> >
> > On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran 
> > wrote:
> >
> > >
> > > > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli <
> vino...@apache.org>
> > > wrote:
> > > >
> > > > We are not converging - there’s still 58 more. I need help from the
> > > community in addressing / review 2.8.0 blockers. If folks can start
> with
> > > reviewing Patch available tickets, that’ll be great.
> > > >
> > > >
> > >
> > >
> > > I'm still doing the s3a stuff, other people testing and reviewing this
> > > stuff welcome.
> > >
> > > in particular, I could do with others playing with this patch of mine,
> > > which adds counters and things into S3a, based on the azure
> > instrumentation
> > >
> > > https://issues.apache.org/jira/browse/HADOOP-13028
> > >
> > >
> > >
> >
>

Re: [Release thread] 2.8.0 release activities

2016-05-11 Thread Wangda Tan

+1, we should close such staled JIRAs to avoid doing unnecessary checks for
every releases.

I'm working on reviewing YARN/MR critical/blocker patches currently, it
gonna very helpful if someone else can help with reviewing Common/HDFS
JIRAs.

Thanks,
Wangda


On Wed, May 11, 2016 at 4:20 PM, Sangjin Lee  wrote:

> Where do we stand in terms of closing out blocker/critical issues for
> 2.8.0? I still see 50 open JIRAs in Vinod's list:
> https://issues.apache.org/jira/issues/?filter=12334985
>
> But I see a lot of JIRAs with no patches or very stale patches. It would be
> a good exercise to come up with the list of JIRAs that we need to block
> 2.8.0 for and focus our attention on closing them out. Thoughts?
>
> Thanks,
> Sangjin
>
> On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran 
> wrote:
>
> >
> > > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli 
> > wrote:
> > >
> > > We are not converging - there’s still 58 more. I need help from the
> > community in addressing / review 2.8.0 blockers. If folks can start with
> > reviewing Patch available tickets, that’ll be great.
> > >
> > >
> >
> >
> > I'm still doing the s3a stuff, other people testing and reviewing this
> > stuff welcome.
> >
> > in particular, I could do with others playing with this patch of mine,
> > which adds counters and things into S3a, based on the azure
> instrumentation
> >
> > https://issues.apache.org/jira/browse/HADOOP-13028
> >
> >
> >
>

Re: [Release thread] 2.8.0 release activities

2016-05-11 Thread Sangjin Lee

Where do we stand in terms of closing out blocker/critical issues for
2.8.0? I still see 50 open JIRAs in Vinod's list:
https://issues.apache.org/jira/issues/?filter=12334985

But I see a lot of JIRAs with no patches or very stale patches. It would be
a good exercise to come up with the list of JIRAs that we need to block
2.8.0 for and focus our attention on closing them out. Thoughts?

Thanks,
Sangjin

On Sat, Apr 23, 2016 at 5:05 AM, Steve Loughran 
wrote:

>
> > On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli 
> wrote:
> >
> > We are not converging - there’s still 58 more. I need help from the
> community in addressing / review 2.8.0 blockers. If folks can start with
> reviewing Patch available tickets, that’ll be great.
> >
> >
>
>
> I'm still doing the s3a stuff, other people testing and reviewing this
> stuff welcome.
>
> in particular, I could do with others playing with this patch of mine,
> which adds counters and things into S3a, based on the azure instrumentation
>
> https://issues.apache.org/jira/browse/HADOOP-13028
>
>
>

Re: [Release thread] 2.8.0 release activities

2016-04-23 Thread Steve Loughran


> On 23 Apr 2016, at 01:24, Vinod Kumar Vavilapalli  wrote:
> 
> We are not converging - there’s still 58 more. I need help from the community 
> in addressing / review 2.8.0 blockers. If folks can start with reviewing 
> Patch available tickets, that’ll be great.
> 
> 


I'm still doing the s3a stuff, other people testing and reviewing this stuff 
welcome. 

in particular, I could do with others playing with this patch of mine, which 
adds counters and things into S3a, based on the azure instrumentation

https://issues.apache.org/jira/browse/HADOOP-13028

Re: [Release thread] 2.8.0 release activities

2016-04-22 Thread Vinod Kumar Vavilapalli

We are not converging - there’s still 58 more. I need help from the community 
in addressing / review 2.8.0 blockers. If folks can start with reviewing Patch 
available tickets, that’ll be great.


Thanks
+Vinod

> On Apr 4, 2016, at 2:16 PM, Vinod Kumar Vavilapalli  
> wrote:
> 
> Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 
> now! : https://issues.apache.org/jira/issues/?filter=12334985
> 
> Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted 
> on branch-2, I figured I have to backport a whole bunch of patches that are 
> only on trunk, and may be more fixes on top of that *sigh*
> 
> I’ll start pushing for progress for an RC in a week or two.
> 
> Any help towards this, reviewing/committing outstanding patches and 
> contributing to open items is greatly appreciated.
> 
> Thanks
> +Vinod
> 
>> On Feb 9, 2016, at 11:51 AM, Vinod Kumar Vavilapalli  
>> wrote:
>> 
>> Sure. The last time I checked, there were 20 odd blocker/critical tickets 
>> too that’ll need some of my time.
>> 
>> Given that, if you can get them in before a week, we should be good.
>> 
>> +Vinod
>> 
>>> On Feb 5, 2016, at 1:19 PM, Subramaniam V K  wrote:
>>> 
>>> Vinod,
>>> 
>>> Thanks for initiating the 2.8 release thread. We are in late review stages
>>> for YARN-4420 (Add REST API for listing reservations) and YARN-2575 (Adding
>>> ACLs for reservation system), hoping to get them by next week. Any chance
>>> you can put off cutting 2.8 by a week as we are planning to deploy
>>> ReservationSystem and these are critical for that?
>>> 
>>> Cheers,
>>> Subru
>>> 
>>> On Thu, Feb 4, 2016 at 3:17 PM, Chris Nauroth 
>>> wrote:
>>> 
 FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0
 release.
 
 --Chris Nauroth
 
 
 
 
 On 2/3/16, 6:19 PM, "Karthik Kambatla"  wrote:
 
> Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me.
> Let us not call it alpha or beta though, it is quite confusing. :)
> 
> On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma  
> wrote:
> 
>> Thanks Vinod. +1 for 2.8 release start.
>> 
>> Regards,
>> Uma
>> 
>> On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" 
>> 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
  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
>  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
>>  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
>> 
>> 
>> 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
>>> 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.
>> 
> 
 
>>> 
>> 
>> 
 
 
>> 
>

Re: [Release thread] 2.8.0 release activities

2016-04-05 Thread Steve Loughran


> On 4 Apr 2016, at 22:16, Vinod Kumar Vavilapalli  wrote:
> 
> Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 
> now! : https://issues.apache.org/jira/issues/?filter=12334985
> 
> Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted 
> on branch-2, I figured I have to backport a whole bunch of patches that are 
> only on trunk, and may be more fixes on top of that *sigh*
> 
> I’ll start pushing for progress for an RC in a week or two.
> 
> Any help towards this, reviewing/committing outstanding patches and 
> contributing to open items is greatly appreciated.
> 


I'm trying to get all the s3a stuff in, hampered by the fact that (a) it's 
spare time and (b) it now takes 1-2h for all the tests to complete, at least 
from my house -> AWS ireland.

Anyone else who can help test/review those s3a patches in HADOOP-11694 is very 
welcome, especially if you test against: different endpoints, different s3 
implementations, use different login mechanims

-Steve

Re: [Release thread] 2.8.0 release activities

2016-04-05 Thread Akira AJISAKA

> Also, the docs target (mvn package -Pdocs -DskipTests) is completely 
busted on branch-2, I figured I have to backport a whole bunch of 
patches that are only on trunk, and may be more fixes on top of that *sigh*


To fix this failure, HADOOP-12022 should be backported to branch-2 and 
branch-2.8. I reopened the issue and rebased the patch.


Thanks,
Akira

On 4/5/16 06:16, Vinod Kumar Vavilapalli wrote:

Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 
now! : https://issues.apache.org/jira/issues/?filter=12334985

Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted on 
branch-2, I figured I have to backport a whole bunch of patches that are only 
on trunk, and may be more fixes on top of that *sigh*

I’ll start pushing for progress for an RC in a week or two.

Any help towards this, reviewing/committing outstanding patches and 
contributing to open items is greatly appreciated.

Thanks
+Vinod


On Feb 9, 2016, at 11:51 AM, Vinod Kumar Vavilapalli  wrote:

Sure. The last time I checked, there were 20 odd blocker/critical tickets too 
that’ll need some of my time.

Given that, if you can get them in before a week, we should be good.

+Vinod


On Feb 5, 2016, at 1:19 PM, Subramaniam V K  wrote:

Vinod,

Thanks for initiating the 2.8 release thread. We are in late review stages
for YARN-4420 (Add REST API for listing reservations) and YARN-2575 (Adding
ACLs for reservation system), hoping to get them by next week. Any chance
you can put off cutting 2.8 by a week as we are planning to deploy
ReservationSystem and these are critical for that?

Cheers,
Subru

On Thu, Feb 4, 2016 at 3:17 PM, Chris Nauroth 
wrote:


FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0
release.

--Chris Nauroth




On 2/3/16, 6:19 PM, "Karthik Kambatla"  wrote:


Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me.
Let us not call it alpha or beta though, it is quite confusing. :)

On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma 
Thanks Vinod. +1 for 2.8 release start.

Regards,
Uma

On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" 
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
 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
 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
 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


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
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.

Re: [Release thread] 2.8.0 release activities

2016-04-04 Thread Vinod Kumar Vavilapalli

Here we go again. The blocker / critical tickets ballooned up a lot, I see 64 
now! : https://issues.apache.org/jira/issues/?filter=12334985

Also, the docs target (mvn package -Pdocs -DskipTests) is completely busted on 
branch-2, I figured I have to backport a whole bunch of patches that are only 
on trunk, and may be more fixes on top of that *sigh*

I’ll start pushing for progress for an RC in a week or two.

Any help towards this, reviewing/committing outstanding patches and 
contributing to open items is greatly appreciated.

Thanks
+Vinod

> On Feb 9, 2016, at 11:51 AM, Vinod Kumar Vavilapalli  
> wrote:
> 
> Sure. The last time I checked, there were 20 odd blocker/critical tickets too 
> that’ll need some of my time.
> 
> Given that, if you can get them in before a week, we should be good.
> 
> +Vinod
> 
>> On Feb 5, 2016, at 1:19 PM, Subramaniam V K  wrote:
>> 
>> Vinod,
>> 
>> Thanks for initiating the 2.8 release thread. We are in late review stages
>> for YARN-4420 (Add REST API for listing reservations) and YARN-2575 (Adding
>> ACLs for reservation system), hoping to get them by next week. Any chance
>> you can put off cutting 2.8 by a week as we are planning to deploy
>> ReservationSystem and these are critical for that?
>> 
>> Cheers,
>> Subru
>> 
>> On Thu, Feb 4, 2016 at 3:17 PM, Chris Nauroth 
>> wrote:
>> 
>>> FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0
>>> release.
>>> 
>>> --Chris Nauroth
>>> 
>>> 
>>> 
>>> 
>>> On 2/3/16, 6:19 PM, "Karthik Kambatla"  wrote:
>>> 
 Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me.
 Let us not call it alpha or beta though, it is quite confusing. :)
 
 On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma >>> 
 wrote:
 
> Thanks Vinod. +1 for 2.8 release start.
> 
> Regards,
> Uma
> 
> On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" 
> 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
>>>  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
  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
>  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
> 
> 
> 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
>> 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.
> 
 
>>> 
>> 
> 
> 
>>> 
>>> 
>

Re: [Release thread] 2.8.0 release activities

2016-02-09 Thread Vinod Kumar Vavilapalli

Sure. The last time I checked, there were 20 odd blocker/critical tickets too 
that’ll need some of my time.

Given that, if you can get them in before a week, we should be good.

+Vinod

> On Feb 5, 2016, at 1:19 PM, Subramaniam V K  wrote:
> 
> Vinod,
> 
> Thanks for initiating the 2.8 release thread. We are in late review stages
> for YARN-4420 (Add REST API for listing reservations) and YARN-2575 (Adding
> ACLs for reservation system), hoping to get them by next week. Any chance
> you can put off cutting 2.8 by a week as we are planning to deploy
> ReservationSystem and these are critical for that?
> 
> Cheers,
> Subru
> 
> On Thu, Feb 4, 2016 at 3:17 PM, Chris Nauroth 
> wrote:
> 
>> FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0
>> release.
>> 
>> --Chris Nauroth
>> 
>> 
>> 
>> 
>> On 2/3/16, 6:19 PM, "Karthik Kambatla"  wrote:
>> 
>>> Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me.
>>> Let us not call it alpha or beta though, it is quite confusing. :)
>>> 
>>> On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma >> 
>>> wrote:
>>> 
 Thanks Vinod. +1 for 2.8 release start.
 
 Regards,
 Uma
 
 On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" 
 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
>>  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
>>>  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
  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
 
 
 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
> 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.
 
>>> 
>> 
> 
 
 
>> 
>>

Re: [Release thread] 2.8.0 release activities

2016-02-05 Thread Subramaniam V K

Vinod,

Thanks for initiating the 2.8 release thread. We are in late review stages
for YARN-4420 (Add REST API for listing reservations) and YARN-2575 (Adding
ACLs for reservation system), hoping to get them by next week. Any chance
you can put off cutting 2.8 by a week as we are planning to deploy
ReservationSystem and these are critical for that?

Cheers,
Subru

On Thu, Feb 4, 2016 at 3:17 PM, Chris Nauroth 
wrote:

> FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0
> release.
>
> --Chris Nauroth
>
>
>
>
> On 2/3/16, 6:19 PM, "Karthik Kambatla"  wrote:
>
> >Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me.
> >Let us not call it alpha or beta though, it is quite confusing. :)
> >
> >On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma  >
> >wrote:
> >
> >> Thanks Vinod. +1 for 2.8 release start.
> >>
> >> Regards,
> >> Uma
> >>
> >> On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" 
> >>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
> >> >> 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
> >> >>> 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
> >>  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
> >> 
> >> 
> >>  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
> >> >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.
> >> 
> >> >>>
> >> >>
> >> >
> >>
> >>
>
>

Re: [Release thread] 2.8.0 release activities

2016-02-04 Thread Chris Nauroth

FYI, I've just needed to raise HDFS-9761 to blocker status for the 2.8.0
release.

--Chris Nauroth




On 2/3/16, 6:19 PM, "Karthik Kambatla"  wrote:

>Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me.
>Let us not call it alpha or beta though, it is quite confusing. :)
>
>On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma 
>wrote:
>
>> Thanks Vinod. +1 for 2.8 release start.
>>
>> Regards,
>> Uma
>>
>> On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli" 
>>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
>> >> 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
>> >>> 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
>>  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
>> 
>> 
>>  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
>> >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.
>> 
>> >>>
>> >>
>> >
>>
>>

Re: [Release thread] 2.8.0 release activities

2016-02-03 Thread Karthik Kambatla

Thanks Vinod. Not labeling 2.8.0 stable sounds perfectly reasonable to me.
Let us not call it alpha or beta though, it is quite confusing. :)

On Wed, Feb 3, 2016 at 8:17 PM, Gangumalla, Uma 
wrote:

> Thanks Vinod. +1 for 2.8 release start.
>
> Regards,
> Uma
>
> On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli"  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
> >> 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
> >>> 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
>  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
> 
> 
>  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
> >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.
> 
> >>>
> >>
> >
>
>

Re: [Release thread] 2.8.0 release activities

2016-02-03 Thread Gangumalla, Uma

Thanks Vinod. +1 for 2.8 release start.

Regards,
Uma

On 2/3/16, 3:53 PM, "Vinod Kumar Vavilapalli"  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
>> 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
>>> 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
 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

 
 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
>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.
 
>>> 
>> 
>

Re: [Release thread] 2.8.0 release activities

2016-02-03 Thread Vinod Kumar Vavilapalli

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  
> 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  
>> 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  
>>> 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 
>>> 
>>> 
>>> 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 
 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.
>>> 
>> 
>

Re: [Release thread] 2.8.0 release activities

2015-11-25 Thread Vinod Kumar Vavilapalli

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  
> 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  
>> 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 
>> 
>> 
>> 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 
>>> 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.
>> 
>

[Release thread] 2.8.0 release activities

2015-11-25 Thread Vinod Kumar Vavilapalli

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  
> 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 
> 
> 
> 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 
>> 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.
>

37 matches

Mail list logo