I'm -0 on rc1. Note the latest discussion on HDFS-6527 which first resulted in that patch being reverted from branch-2.4.1 because it was believed it wasn't necessary, and then some more discussion which indicates that in fact the patch for HDFS-6527 should be included in 2.4.1, but with a slightly different test case.
I believe that rc1 was actually created after the first backport of HDFS-6527, but before the revert, so rc1 should be functionally correct, but the test case is not quite correct in rc1, and I believe that rc1 does not currently reflect the actual tip of branch-2.4.1. I'm not going to consider this a deal-breaker, but seems like we should probably clean it up. To get this all sorted out properly, if we wanted to, I believe we should do another backport of HDFS-6527 to branch-2.4.1 including only the amended test case, and create a new RC from that point. Best, Aaron -- Aaron T. Myers Software Engineer, Cloudera On Fri, Jun 20, 2014 at 11:51 PM, Arun C Murthy <a...@hortonworks.com> wrote: > Folks, > > I've created another release candidate (rc1) for hadoop-2.4.1 based on the > feedback that I would like to push out. > > The RC is available at: > http://people.apache.org/~acmurthy/hadoop-2.4.1-rc1 > The RC tag in svn is here: > https://svn.apache.org/repos/asf/hadoop/common/tags/release-2.4.1-rc1 > > 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/hdp/ > > > > -- > CONFIDENTIALITY NOTICE > 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. >