* Andrew Wang <andrew.w...@cloudera.com>
>> *Sent:* Friday, January 20, 2017 10:48 AM
>> *To:* Junping Du
>> *Cc:* common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
>> mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org
>>
>> *Subject:*
___
> From: Andrew Wang <andrew.w...@cloudera.com>
> Sent: Friday, January 20, 2017 10:48 AM
> To: Junping Du
> Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org
> Subject: Re: [Continued] [
cloudera.com>
> *Sent:* Friday, January 20, 2017 10:48 AM
> *To:* Junping Du
> *Cc:* common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org
>
> *Subject:* Re: [Continued] [Release thread] 2.8.0 release activities
>
:48 AM
To: Junping Du
Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
mapreduce-dev@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 Sig
rtonworks.com>
> Sent: Thursday, January 19, 2017 6:46 PM
> To: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org
> Cc: Varun Vasudev
> Subject: Re: [Continued] [Release thread] 2.8.0 release activities
>
> According to
udev
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
; 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-60
he.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 c
016 12:12 AM
To: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
mapreduce-dev@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
; hdfs-...@hadoop.apache.org;
mapreduce-dev@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.apac
ct: 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, J
vilapalli; 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://buil
.@apache.org>
> Sent: Wednesday, November 30, 2016 3:24 PM
> To: Junping Du
> Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
> mapreduce-dev@hadoop.apache.org; yarn-...@hadoop.apache.org; Vinod
> Vavilapalli; Jian He; Wangda Tan; sj...@twitter.com
> Subject:
u
Cc: common-...@hadoop.apache.org; hdfs-...@hadoop.apache.org;
mapreduce-dev@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 e
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
15 matches
Mail list logo