We should be able to ship YARN HA in Jan. We are two sub-tasks away from main functionality (patches in progress for both). YARN-149 has some duplicate sub-tasks. We should definitely be able to test / fix any critical issues by Jan.
On Thu, Dec 5, 2013 at 3:57 PM, Arun C Murthy <a...@hortonworks.com> wrote: > Ok, I've updated https://wiki.apache.org/hadoop/Roadmap with a initial > strawman list for hadoop-2.4 which I feel we can get out in Jan. > > What else would folks like to see? Please keep timeframe in mind. > > thanks, > Arun > > On Dec 2, 2013, at 10:55 AM, Arun C Murthy <a...@hortonworks.com> wrote: > > > > > On Nov 13, 2013, at 1:55 PM, Jason Lowe <jl...@yahoo-inc.com> wrote: > >> > >> > >> +1 to limiting checkins of patch releases to Blockers/Criticals. If > necessary committers check into trunk/branch-2 only and defer to the patch > release manager for the patch release merge. Then there should be fewer > surprises for everyone what ended up in a patch release and less likely the > patch release becomes destabilized from the sheer amount of code churn. > Maybe this won't be necessary if everyone understands that the patch > release isn't the only way to get a change out in timely manner. > > > > I've updated https://wiki.apache.org/hadoop/Roadmap to reflect that we > only put in Blocker/Critical bugs into Point Releases. > > > > Committers, from now, please exercise extreme caution when committing to > a point release: they should only be limited to Blocker bugs. > > > > thanks, > > Arun > > > > -- > Arun C. Murthy > Hortonworks Inc. > http://hortonworks.com/ > > > > -- > 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. >
