Return-Path: X-Original-To: apmail-hive-dev-archive@www.apache.org Delivered-To: apmail-hive-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DC97B10A9D for ; Tue, 4 Mar 2014 17:25:10 +0000 (UTC) Received: (qmail 69594 invoked by uid 500); 4 Mar 2014 17:25:08 -0000 Delivered-To: apmail-hive-dev-archive@hive.apache.org Received: (qmail 69543 invoked by uid 500); 4 Mar 2014 17:25:05 -0000 Mailing-List: contact dev-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hive.apache.org Delivered-To: mailing list dev@hive.apache.org Received: (qmail 69535 invoked by uid 99); 4 Mar 2014 17:25:04 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Mar 2014 17:25:04 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of gates@hortonworks.com designates 209.85.160.42 as permitted sender) Received: from [209.85.160.42] (HELO mail-pb0-f42.google.com) (209.85.160.42) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 04 Mar 2014 17:25:00 +0000 Received: by mail-pb0-f42.google.com with SMTP id rr13so5469702pbb.15 for ; Tue, 04 Mar 2014 09:24:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date :message-id:references:to:content-type:content-transfer-encoding; bh=d3o33X8dq0t0jUzRV0bYOe5jqtgO0a8dEIyeNidzyhQ=; b=XuNWSNhKiwWWI1uC3JyI7fh/dOjMtd9qchwhpcr24YOxGCBGV1KRmwUCzPc/tCaMoM VwX8Bcv31fg9KNV4ZuF4pPTfZGn35XwHiIqYKHUOOsyHk9WlZJ00+1aUDLWVRGXPMlQ/ vwIEhKQMjzCgj+HTHZY0fll9SLJrsND5CjbkCuJ2wRTkszz6ErEJb4Oiux7v8fXkHkVo 3p3pNec6lh/n8DmdiXb1p4hbnqsS/MEWRBhEL37q0UQkNKX1dQcllCzCQZuguqdfuebn 3M/V1xqTASRpGup2U1t15bV7HH2u0XnAvHylckgi3vo6zj987nMAWg4E7QPpxUlCqbCn RQYw== X-Gm-Message-State: ALoCoQnL5MsXvcNHL7UhBU00AgAD8L0FkHmfBGzcbhTcWzSelbCVvI/pqUkinh+0FbOkPSR6TYeMWMQxOqFHsRH8wwpZV3XebA4sUirpTB3/RfbwDVS0O4U= X-Received: by 10.67.14.69 with SMTP id fe5mr837263pad.120.1393953568041; Tue, 04 Mar 2014 09:19:28 -0800 (PST) Received: from [10.11.2.66] ([192.175.27.2]) by mx.google.com with ESMTPSA id qs1sm49880254pbb.18.2014.03.04.09.19.26 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 04 Mar 2014 09:19:26 -0800 (PST) Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Timeline for the Hive 0.13 release? From: Alan Gates In-Reply-To: <9FBC9A5B-40F6-46B2-99ED-779023B96469@hortonworks.com> Date: Tue, 4 Mar 2014 08:03:24 -0800 Message-Id: <00D59C7A-0F1F-4995-A7D3-9414D09F152E@hortonworks.com> References: <1D2D7558-1846-4F28-944A-139675BBAE5B@hortonworks.com> <9FBC9A 5B-40F6-46B2-99ED-779023B96469@hortonworks.com> To: dev@hive.apache.org X-Mailer: Apple Mail (2.1874) Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Sure. I=E2=80=99d really like to get the work related to HIVE-5317 in 0.13= . HIVE-5843 is patch available and hopefully can be checked in today. The= re are several more that depend on that one and can=E2=80=99t be made patch= available until then (HIVE-6060, HIVE-6319, HIVE-6460, and HIVE-5687). I = don=E2=80=99t want to hold up the branching, but are you ok with those goin= g in after the branch? Alan. On Mar 3, 2014, at 7:53 PM, Harish Butani wrote: > I plan to create the branch 5pm PST tomorrow. > Ok with everybody? >=20 > regards, > Harish. >=20 > On Feb 21, 2014, at 5:44 PM, Lefty Leverenz wro= te: >=20 >> That's appropriate -- let the Hive release march forth on March 4th. >>=20 >>=20 >> -- Lefty >>=20 >>=20 >> On Fri, Feb 21, 2014 at 4:04 PM, Harish Butani = wrote: >>=20 >>> Ok,let=E2=80=99s set it for March 4th . >>>=20 >>> regards, >>> Harish. >>>=20 >>> On Feb 21, 2014, at 12:14 PM, Brock Noland wrote: >>>=20 >>>> Might as well make it March 4th or 5th. Otherwise folks will burn >>>> weekend time to get patches in. >>>>=20 >>>> On Fri, Feb 21, 2014 at 2:10 PM, Harish Butani >>> wrote: >>>>> Yes makes sense. >>>>> How about we postpone the branching until 10am PST March 3rd, which i= s >>> the following Monday. >>>>> Don=E2=80=99t see a point of setting the branch time to a Friday even= ing. >>>>> Do people agree? >>>>>=20 >>>>> regards, >>>>> Harish. >>>>>=20 >>>>> On Feb 21, 2014, at 11:04 AM, Brock Noland wrote= : >>>>>=20 >>>>>> +1 >>>>>>=20 >>>>>> On Fri, Feb 21, 2014 at 1:02 PM, Thejas Nair >>> 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 >>>>>>>=20 >>>>>>>=20 >>>>>>>=20 >>>>>>> On Sun, Feb 16, 2014 at 5:32 PM, Brock Noland >>> wrote: >>>>>>>=20 >>>>>>>> I'd love to see HIVE-6037 in the 0.13 release. I have +1'ed it >>> pending >>>>>>>> tests. >>>>>>>>=20 >>>>>>>> Brock >>>>>>>>=20 >>>>>>>> On Sun, Feb 16, 2014 at 7:23 PM, Navis=EB=A5=98=EC=8A=B9=EC=9A=B0 = >>> 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). >>>>>>>>>=20 >>>>>>>>>=20 >>>>>>>>> 2014-02-16 20:38 GMT+09:00 Lefty Leverenz >>> : >>>>>>>>>=20 >>>>>>>>>> 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 promis= es. >>>>>>>>>>=20 >>>>>>>>>> Feel free to do your own documentation, or hand it off to a >>> friendly >>>>>>>>>> in-house writer. >>>>>>>>>>=20 >>>>>>>>>> -- Lefty, self-appointed Hive docs maven >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> On Sat, Feb 15, 2014 at 1:28 PM, Thejas Nair < >>> thejas@hortonworks.com> >>>>>>>>>> wrote: >>>>>>>>>>=20 >>>>>>>>>>> Sounds good to me. >>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> On Fri, Feb 14, 2014 at 7:29 PM, Harish Butani < >>>>>>>> hbutani@hortonworks.com >>>>>>>>>>>> wrote: >>>>>>>>>>>=20 >>>>>>>>>>>> Hi, >>>>>>>>>>>>=20 >>>>>>>>>>>> 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. >>>>>>>>>>>>=20 >>>>>>>>>>>> regards, >>>>>>>>>>>> Harish. >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> On Jan 20, 2014, at 9:25 AM, Brock Noland >>>>>>>> wrote: >>>>>>>>>>>>=20 >>>>>>>>>>>>> Hi, >>>>>>>>>>>>>=20 >>>>>>>>>>>>> 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. >>>>>>>>>>>>>=20 >>>>>>>>>>>>> Brock >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> On Sat, Jan 18, 2014 at 4:21 PM, Harish Butani < >>>>>>>>>>> hbutani@hortonworks.com >>>>>>>>>>>>> wrote: >>>>>>>>>>>>>=20 >>>>>>>>>>>>>> Yes agree it is time to start planning for the next release. >>>>>>>>>>>>>> I would like to volunteer to do the release management dutie= s >>> for >>>>>>>>>> this >>>>>>>>>>>>>> release(will be a great experience for me) >>>>>>>>>>>>>> Will be happy to do it, if the community is fine with this. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> regards, >>>>>>>>>>>>>> Harish. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> On Jan 17, 2014, at 7:05 PM, Thejas Nair < >>> thejas@hortonworks.com >>>>>>>>>=20 >>>>>>>>>>>> wrote: >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Yes, I think it is time to start planning for the next >>> release. >>>>>>>>>>>>>>> For 0.12 release I created a branch and then accepted patch= es >>>>>>>> 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 i= n >>>>>>>> only >>>>>>>>>>>>>>> critical bug fixes to the branch after that. >>>>>>>>>>>>>>> How about cutting the branch around mid-February and target= ing >>>>>>>> to >>>>>>>>>>>>>>> release in a week or two after that. >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> Thanks, >>>>>>>>>>>>>>> Thejas >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> On Fri, Jan 17, 2014 at 4:39 PM, Carl Steinbach < >>> cws@apache.org >>>>>>>>>=20 >>>>>>>>>>>> wrote: >>>>>>>>>>>>>>>> I was wondering what people think about setting a tentativ= e >>>>>>>> date >>>>>>>>>> for >>>>>>>>>>>> the >>>>>>>>>>>>>>>> Hive 0.13 release? At an old Hive Contrib meeting we agree= d >>>>>>>> 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. >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> Thoughts? >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> Thanks. >>>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>>> Carl >>>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>> -- >>>>>>>>>>>>>>> CONFIDENTIALITY NOTICE >>>>>>>>>>>>>>> NOTICE: This message is intended for the use of the individ= ual >>>>>>>> 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 here= by >>>>>>>>>>> notified >>>>>>>>>>>>>> that >>>>>>>>>>>>>>> any printing, copying, dissemination, distribution, disclos= ure >>>>>>>> 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. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> CONFIDENTIALITY NOTICE >>>>>>>>>>>>>> NOTICE: This message is intended for the use of the individu= al >>> 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 hereb= y >>>>>>>>>> notified >>>>>>>>>>>> that >>>>>>>>>>>>>> any printing, copying, dissemination, distribution, disclosu= re >>> or >>>>>>>>>>>>>> forwarding of this communication is strictly prohibited. If = you >>>>>>>> have >>>>>>>>>>>>>> received this communication in error, please contact the sen= der >>>>>>>>>>>> immediately >>>>>>>>>>>>>> and delete it from your system. Thank You. >>>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>>=20 >>>>>>>>>>>>> -- >>>>>>>>>>>>> Apache MRUnit - Unit testing MapReduce - >>> http://mrunit.apache.org >>>>>>>>>>>>=20 >>>>>>>>>>>>=20 >>>>>>>>>>>> -- >>>>>>>>>>>> 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 yo= u >>> have >>>>>>>>>>>> received this communication in error, please contact the sende= r >>>>>>>>>>> immediately >>>>>>>>>>>> and delete it from your system. Thank You. >>>>>>>>>>>>=20 >>>>>>>>>>>=20 >>>>>>>>>>> -- >>>>>>>>>>> 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. >>>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> -- >>>>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org >>>>>>>>=20 >>>>>>>=20 >>>>>>> -- >>>>>>> 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 hav= e >>>>>>> received this communication in error, please contact the sender >>> immediately >>>>>>> and delete it from your system. Thank You. >>>>>>=20 >>>>>>=20 >>>>>>=20 >>>>>> -- >>>>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org >>>>>=20 >>>>>=20 >>>>> -- >>>>> 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 confidentia= l, >>>>> privileged and exempt from disclosure under applicable law. If the >>> reader >>>>> of this message is not the intended recipient, you are hereby notifie= d >>> 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. >>>>=20 >>>>=20 >>>>=20 >>>> -- >>>> Apache MRUnit - Unit testing MapReduce - http://mrunit.apache.org >>>=20 >>>=20 >>> -- >>> CONFIDENTIALITY NOTICE >>> NOTICE: This message is intended for the use of the individual or entit= y to >>> which it is addressed and may contain information that is confidential, >>> privileged and exempt from disclosure under applicable law. If the read= er >>> 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 immedia= tely >>> and delete it from your system. Thank You. >>>=20 >=20 >=20 > --=20 > CONFIDENTIALITY NOTICE > NOTICE: This message is intended for the use of the individual or entity = to=20 > which it is addressed and may contain information that is confidential,= =20 > privileged and exempt from disclosure under applicable law. If the reader= =20 > of this message is not the intended recipient, you are hereby notified th= at=20 > any printing, copying, dissemination, distribution, disclosure or=20 > forwarding of this communication is strictly prohibited. If you have=20 > received this communication in error, please contact the sender immediate= ly=20 > and delete it from your system. Thank You. --=20 CONFIDENTIALITY NOTICE NOTICE: This message is intended for the use of the individual or entity to= =20 which it is addressed and may contain information that is confidential,=20 privileged and exempt from disclosure under applicable law. If the reader= =20 of this message is not the intended recipient, you are hereby notified that= =20 any printing, copying, dissemination, distribution, disclosure or=20 forwarding of this communication is strictly prohibited. If you have=20 received this communication in error, please contact the sender immediately= =20 and delete it from your system. Thank You.