We are looking forward to Hive 0.13. For Tez and other cool features, we'd like to try it on our Yarn cluster.
Thanks, Zhuoluo (Clark) Yang 2014-02-16 19:38 GMT+08:00 Lefty Leverenz <leftylever...@gmail.com>: > I'll try to catch up on the wikidocs backlog for 0.13.0 patches in time for > the release. It's a long and growing list, though, so no promises. > > Feel free to do your own documentation, or hand it off to a friendly > in-house writer. > > -- Lefty, self-appointed Hive docs maven > > > > On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair <the...@hortonworks.com> > wrote: > > > Sounds good to me. > > > > > > On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani <hbut...@hortonworks.com > > >wrote: > > > > > Hi, > > > > > > Its mid feb. Wanted to check if the community is ready to cut a branch. > > > Could we cut the branch in a week , say 5pm PST 2/21/14? > > > The goal is to keep the release cycle short: couple of weeks; so after > > the > > > branch we go into stabilizing mode for hive 0.13, checking in only > > > blocker/critical bug fixes. > > > > > > regards, > > > Harish. > > > > > > > > > On Jan 20, 2014, at 9:25 AM, Brock Noland <br...@cloudera.com> wrote: > > > > > > > Hi, > > > > > > > > I agree that picking a date to branch and then restricting commits to > > > that > > > > branch would be a less time intensive plan for the RM. > > > > > > > > Brock > > > > > > > > > > > > On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani < > > hbut...@hortonworks.com > > > >wrote: > > > > > > > >> Yes agree it is time to start planning for the next release. > > > >> I would like to volunteer to do the release management duties for > this > > > >> release(will be a great experience for me) > > > >> Will be happy to do it, if the community is fine with this. > > > >> > > > >> regards, > > > >> Harish. > > > >> > > > >> On Jan 17, 2014, at 7:05 PM, Thejas Nair <the...@hortonworks.com> > > > wrote: > > > >> > > > >>> Yes, I think it is time to start planning for the next release. > > > >>> For 0.12 release I created a branch and then accepted patches that > > > >>> people asked to be included for sometime, before moving a phase of > > > >>> accepting only critical bug fixes. This turned out to be laborious. > > > >>> I think we should instead give everyone a few weeks to get any > > patches > > > >>> they are working on to be ready, cut the branch, and take in only > > > >>> critical bug fixes to the branch after that. > > > >>> How about cutting the branch around mid-February and targeting to > > > >>> release in a week or two after that. > > > >>> > > > >>> Thanks, > > > >>> Thejas > > > >>> > > > >>> > > > >>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach <c...@apache.org> > > > wrote: > > > >>>> I was wondering what people think about setting a tentative date > for > > > the > > > >>>> Hive 0.13 release? At an old Hive Contrib meeting we agreed that > > Hive > > > >>>> should follow a time-based release model with new releases every > > four > > > >>>> months. If we follow that schedule we're due for the next release > in > > > >>>> mid-February. > > > >>>> > > > >>>> Thoughts? > > > >>>> > > > >>>> Thanks. > > > >>>> > > > >>>> Carl > > > >>> > > > >>> -- > > > >>> 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. > > > >> > > > > > > > > > > > > > > > > -- > > > > Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org > > > > > > > > > -- > > > 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. > > >
