hadoop-yarn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vinod Kumar Vavilapalli <vino...@apache.org>
Subject [VOTE] Release Apache Hadoop 2.6.1 RC0
Date Thu, 10 Sep 2015 01:00:25 GMT
 Hi all,

After a nearly month long [1] toil, with loads of help from Sangjin Lee and
Akira Ajisaka, and 153 commits later, I've created a release candidate RC0
for hadoop-2.6.1.

The RC is available at: http://people.apache.org/~vinodkv/hadoop-2.6.1-RC0/

The RC tag in git is: release-2.6.1-RC0

The maven artifacts are available via repository.apache.org at

Some notes from our release process
 -  - Sangjin and I moved out a bunch of items pending from 2.6.1 [2] -
non-committed but desired patches. 2.6.1 is already big as is and is late
by any standard, we can definitely include them in the next release.
 - The 2.6.1 wiki page [3] captures some (but not all) of the context of
the patches that we pushed in.
 - Given the number of fixes pushed [4] in, we had to make a bunch of
changes to our original plan - we added a few improvements that helped us
backport patches easier (or in many cases made backports possible), and we
dropped a few that didn't make sense (HDFS-7831, HDFS-7926, HDFS-7676,
HDFS-7611, HDFS-7843, HDFS-8850).
 - I ran all the unit tests which (surprisingly?) passed. (Except for one,
which pointed out a missing fix HDFS-7552).

As discussed before [5]
 - This release is the first point release after 2.6.0
 - I’d like to use this as a starting release for 2.6.2 in a few weeks and
then follow up with more of these.

Please try the release and vote; the vote will run for the usual 5 days.


[1] Hadoop 2.6.1 Release process thread:
[2] 2.6.1 Pending tickets:
[3] 2.6.1 Wiki page:
[4] List of 2.6.1 patches pushed:
[5] Planning Hadoop 2.6.1 release:

 - Note that branch-2.6 which will be the base for 2.6.2 doesn't have these
fixes yet. Once 2.6.1 goes through, I plan to rebase branch-2.6 based off
 - Patches that got into 2.6.1 all the way from 2.8 are NOT in 2.7.2 yet,
this will be done as a followup.

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