hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Arun C Murthy <...@hortonworks.com>
Subject Re: Logistics for releasing 2.4
Date Tue, 21 Jan 2014 19:12:42 GMT

 I'm almost ready to push out rc0 for 2.3 (been testing it overnight), I'm pretty sure I'll
get that out tonight.

 However, AHS (YARN-321) is very close (merge vote going on) … so that will definitely make
it in very soon.

 So, my plan is essentially the same i.e. release 2.4 end of the month (after a bit more testing
of RM HA in secure mode). Thanks for the offer, I'll ping you if I need any help.

 OTOH, can someone from HDFS chime in on status of symlinks?


On Jan 20, 2014, at 4:19 PM, Andrew Wang <andrew.wang@cloudera.com> wrote:

> Hi all,
> I'm pretty excited to see a 2.4 this month if possible. Since I think
> people were favorable to the idea of time-based releases, how do we feel
> about just cutting branch-2 and spinning up the release process for our
> January goal?
> Looking at the roadmap (https://wiki.apache.org/hadoop/Roadmap), on the
> HDFS side, I plan to post a branch-2 patch for HDFS-4949 this week, and
> HDFS-2832 is already in. On the YARN side, it appears that RM HA is in, but
> the other three features (AHS, unmanaged containers, and dynamic resource
> configuration) remain unresolved.
> I think a 2.4 with HDFS-4949, HDFS-2832, and YARN-149 is already a pretty
> nice release. If it'd help, I'm willing to volunteer as release manager to
> help get this out the door.
> Thoughts welcome!
> Thanks,
> Andrew

Arun C. Murthy
Hortonworks Inc.

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.

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