Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
MapReduce >> mail # dev >> [VOTE] Release Apache Hadoop 2.1.1-beta

Copy link to this message
Re: [VOTE] Release Apache Hadoop 2.1.1-beta
Thanks Arun.


* Downloaded source tarball.
* Verified MD5
* Verified signature
* run apache-rat:check ok after minor tweak (see NIT1 below)
* checked CHANGES.txt headers (see NIT2 below)
* built DIST from source
* verified hadoop version of Hadoop JARs
* configured pseudo cluster
* tested HttpFS
* run a few MR examples
* run a few unmanaged AM app examples

The following NITs should be addressed if there is a new RC or in the next

NIT1, empty files that make apache-rat:check to fail, these files should be



NIT2, common/hdfs/mapreduce/yarn CHANGES.txt have 2.2.0 header, they should

On Tue, Sep 17, 2013 at 8:38 AM, Arun C Murthy <[EMAIL PROTECTED]> wrote:

> Folks,
> I've created a release candidate (rc0) for hadoop-2.1.1-beta that I would
> like to get released - this release fixes a number of bugs on top of
> hadoop-2.1.0-beta as a result of significant amounts of testing.
> If things go well, this might be the last of the *beta* releases of
> hadoop-2.x.
> The RC is available at:
> http://people.apache.org/~acmurthy/hadoop-2.1.1-beta-rc0
> The RC tag in svn is here:
> http://svn.apache.org/repos/asf/hadoop/common/tags/release-2.1.1-beta-rc0
> The maven artifacts are available via repository.apache.org.
> Please try the release and vote; the vote will run for the usual 7 days.
> thanks,
> Arun
> --
> Arun C. Murthy
> Hortonworks Inc.
> http://hortonworks.com/
> --
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.