If 2.7 is being positioned as the JDK7-only release, then it would be good to know how 2.8 lines up in terms of timing. Our interest is landing the shared cache feature (YARN-1492)... Thanks.
Sangjin On Mon, Dec 1, 2014 at 2:55 PM, Karthik Kambatla <ka...@cloudera.com> wrote: > Thanks for starting this thread, Arun. > > Your proposal seems reasonable to me. I suppose we would like new features > and improvements to go into 2.8 then? If yes, what time frame are we > looking at for 2.8? Looking at YARN, it would be nice to get a release with > shared-cache and a stable version of reservation work. I believe they are > well under way and should be ready in a few weeks. > > Regarding 2.7 release specifics, do you plan to create a branch off of > current branch-2.6 and update all issues marked fixed for 2.7 to be fixed > for 2.8? > > Thanks > Karthik > > On Mon, Dec 1, 2014 at 2:42 PM, Arun Murthy <a...@hortonworks.com> wrote: > > > Folks, > > > > With hadoop-2.6 out it's time to think ahead. > > > > As we've discussed in the past, 2.6 was the last release which supports > > JDK6. > > > > I'm thinking it's best to try get 2.7 out in a few weeks (maybe by the > > holidays) with just the switch to JDK7 (HADOOP-10530) and possibly > > support for JDK-1.8 (as a runtime) via HADOOP-11090. > > > > This way we can start with the stable base of 2.6 and switch over to > > JDK7 to allow our downstream projects to use either for a short time > > (hadoop-2.6 or hadoop-2.7). > > > > I'll update the Roadmap wiki accordingly. > > > > Thoughts? > > > > thanks, > > Arun > > > > -- > > 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. > > >
