hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Brahma Reddy Battula <brahmareddy.batt...@hotmail.com>
Subject Re: [VOTE] Release Apache Hadoop 2.6.5 (RC0)
Date Sun, 02 Oct 2016 04:13:39 GMT

I am not sure whether we can stop RC or not. But it will be good to have all commits in CHANGES.txt.

Theoretically it should be fine to ensure  bythetime vote pass(As there are no source code
commit missed).Let's somebody else pitch in this.

Bytheway for branch-2.7, I raised HADOOP-13670 to track and even I sent mail for attention.

Thanks And Regards
Brahma Reddy Battula

From: sjlee0@gmail.com <sjlee0@gmail.com> on behalf of Sangjin Lee <sjlee@apache.org>
Sent: Sunday, October 2, 2016 6:10 AM
To: Brahma Reddy Battula
Cc: common-dev@hadoop.apache.org; hdfs-dev@hadoop.apache.org; yarn-dev@hadoop.apache.org;
Subject: Re: [VOTE] Release Apache Hadoop 2.6.5 (RC0)

I took a look at the commits that are part of 2.6.5, and sadly I count a total of 18 of them
that either are missing the corresponding entries or have incorrect release versions in CHANGES.txt.
And I'm not even thinking about possible missing entries in earlier releases. :(

I think us committers need to pay greater attention to detail when we port fixes to 2.6.x
and 2.7.x where CHANGES.txt are still used. The rate of missing entries in CHANGES.txt is
too high.

Due to this high number of missing entries, I am leaning towards cutting another RC where
at least 2.6.5 entries all fixed. Let me know what you all think (whether this is something
that should stop the RC).


On Sat, Oct 1, 2016 at 12:46 PM, Sangjin Lee <sjlee@apache.org<mailto:sjlee@apache.org>>
Thanks John and Brahma for reporting issues with CHANGES.txt.

IMO, we can move ahead with the current RC0 and address these issues in a commit after the
release, but I'm not against cutting another RC to fix CHANGES.txt. What do you think?


On Fri, Sep 30, 2016 at 9:25 PM, Brahma Reddy Battula <brahmareddy.battula@hotmail.com<mailto:brahmareddy.battula@hotmail.com>>

Thanks Sangjin!

+1 ( non- binding)

--Downloaded the source and complied

--Installed HA cluster

--Verified basic fsshell commands

---Did the regression on issues which is handled by me

--Ran pi,terasort Slive jobs, all works fine.

Happy to see HDFS-9530.

Read through the commit log,Seems to be following commits are missed in changes.txt.






--Brahma Reddy Battula

From: sjlee0@gmail.com<mailto:sjlee0@gmail.com> <sjlee0@gmail.com<mailto:sjlee0@gmail.com>>
on behalf of Sangjin Lee <sjlee@apache.org<mailto:sjlee@apache.org>>
Sent: Wednesday, September 28, 2016 1:58 AM
To: common-dev@hadoop.apache.org<mailto:common-dev@hadoop.apache.org>; hdfs-dev@hadoop.apache.org<mailto:hdfs-dev@hadoop.apache.org>;
yarn-dev@hadoop.apache.org<mailto:yarn-dev@hadoop.apache.org>; mapreduce-dev@hadoop.apache.org<mailto:mapreduce-dev@hadoop.apache.org>
Subject: [VOTE] Release Apache Hadoop 2.6.5 (RC0)

Hi folks,

I have created a release candidate RC0 for the Apache Hadoop 2.6.5 release
(the next maintenance release in the 2.6.x release line). Below are the
details of this release candidate:

The RC is available for validation at:

The RC tag in git is release-2.6.5-RC0 and its git commit is

The maven artifacts are staged via repository.apache.org<http://repository.apache.org>

You can find my public key at

Please try the release and vote. The vote will run for the usual 5 days.
Huge thanks to Chris Trezzo for spearheading the release management and
doing all the work!


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message