+1 for starting to think about 2.5. Early June seems a little early to me - we had talked about a quarterly release cadence and this would be about half that.
I'm having trouble editing the wiki, but I think Timeline Server stability (e.g. security and locking down APIs) should go on that list. I think we should probably take YARN-1404 off the list - even with 3 months it's unlikely to be complete. On Sat, Apr 12, 2014 at 9:50 AM, Chris Nauroth <cnaur...@hortonworks.com>wrote: > +1 > > The proposed content for 2.5 in the roadmap wiki looks good to me. > On Apr 12, 2014 7:26 AM, "Arun C Murthy" <a...@hortonworks.com> wrote: > > > Gang, > > > > With hadoop-2.4 out, it's time to think ahead. > > > > In the short-term hadoop-2.4.1 is in order; particularly with > > https://issues.apache.org/jira/browse/MAPREDUCE-5830 (it's a break to > > @Private API, unfortunately something Hive is using - sigh!). There are > > some other fixes which testing has uncovered; so it will be nice to pull > > them them in. I'm thinking of an RC by end of the coming week - > committers, > > please be *very* conservative when getting stuff into 2.4.1 (i.e. merging > > to branch-2.4). > > > > Next up, hadoop-2.5. > > > > I've updated https://wiki.apache.org/hadoop/Roadmap with some > candidates > > for consideration - please chime in and say 'aye'/'nay' or add new > content. > > IAC, I suspect that list is too large. > > > > Rather than wait for everything it would be better to plan on releasing > > it on a time-bound manner; particularly around the Hadoop Summit. If that > > makes sense; I think we should target branching for 2.5 by mid-May to get > > it stable and released by early June. > > > > Thoughts? > > > > 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. > > > > -- > 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. >
