Ok,let’s set it for March 4th . regards, Harish.
On Feb 21, 2014, at 12:14 PM, Brock Noland <br...@cloudera.com> wrote: > Might as well make it March 4th or 5th. Otherwise folks will burn > weekend time to get patches in. > > On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani <hbut...@hortonworks.com> > wrote: >> Yes makes sense. >> How about we postpone the branching until 10am PST March 3rd, which is the >> following Monday. >> Don’t see a point of setting the branch time to a Friday evening. >> Do people agree? >> >> regards, >> Harish. >> >> On Feb 21, 2014, at 11:04 AM, Brock Noland <br...@cloudera.com> wrote: >> >>> +1 >>> >>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair <the...@hortonworks.com> wrote: >>>> Can we wait for some few more days for the branching ? I have a few more >>>> security fixes that I would like to get in, and we also have a long >>>> pre-commit queue ahead right now. How about branching around Friday next >>>> week ? By then hadoop 2.3 should also be out as that vote has been >>>> concluded, and we can get HIVE-6037 in as well. >>>> -Thejas >>>> >>>> >>>> >>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland <br...@cloudera.com> wrote: >>>> >>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it pending >>>>> tests. >>>>> >>>>> Brock >>>>> >>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis류승우 <navis....@nexr.com> wrote: >>>>>> HIVE-6037 is for generating hive-default.template file from HiveConf. >>>>> Could >>>>>> it be included in this release? If it's not, I'll suspend further >>>>> rebasing >>>>>> of it till next release (conflicts too frequently). >>>>>> >>>>>> >>>>>> 2014-02-16 20:38 GMT+09: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. >>>>>>>> >>>>>>> >>>>> >>>>> >>>>> >>>>> -- >>>>> 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. >>> >>> >>> >>> -- >>> 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. > > > > -- > 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.
