I just sent out the announce mail for 1.2.1. I have now updated the wiki page to reflect rules for further commits to branch-1.2:
a) The commit must not introduce any schema or interface changes. b) The commit must fix a bug that causes an outage/breakage (such as an NPE) in regular hive operation, or it must fix a data corruption issue or it must be a security fix with an appropriate CVE. If it meets those bars, you do not need to cc me or ask for my permission, you may go ahead and commit to branch-1.2, and I will keep watch on this branch. If it does not meet those bars, you are directed to target branch-1 or master instead. The goal for an eventual 1.2.2 is to ensure that this branch stays live for breaking fixes, but not so that we may keep landing new patches in released branches. Thanks all! -Sushanth On Tue, Jun 23, 2015 at 11:45 AM, Sushanth Sowmyan <khorg...@gmail.com> wrote: > Thanks for testing and verifying, folks! > > With 4 PMC votes and 105 hours( >72 hours ) now having passed, the > vote for releasing 1.2.1 RC0 as Hive 1.2.1 passes. I will go ahead and > publish artifacts for the 1.2.1 release and send out mail about > general availability. > > With this release, please note that commits to branch-1.2 are now > restricted to a higher bar of necessity, and will require it to be > fixing a product outage(such as an NPE when you run a query). I will > update the wiki to that effect to indicate the process for further > commits to the branch. For most part, please restrict commits to > branch-1 and master from now on. > > I am amenable to doing a 1.2.2 release eventually if we have enough > such issues, maybe about 3+ months out. > > Thanks all! > -Sushanth > > > > On Sun, Jun 21, 2015 at 6:13 PM, Vikram Dixit K <vikram.di...@gmail.com> > wrote: >> +1 built on both profiles and ran a simple query on the rc. >> >> Thanks >> Vikram. >> >> On Sat, Jun 20, 2015 at 7:47 AM, Thejas Nair <thejas.n...@gmail.com> wrote: >>> +1 >>> Checked signatures, checksums >>> Checked release notes >>> Reviewed changes in pom files. >>> Built with hadoop2 and hadoop1. Ran some simple queries in local mode. >>> >>> >>> On Fri, Jun 19, 2015 at 5:00 PM, Gunther Hagleitner < >>> ghagleit...@hortonworks.com> wrote: >>> >>>> +1 Checked signatures, compiled, ran some tests. >>>> >>>> >>>> Thanks, >>>> Gunther. >>>> ------------------------------ >>>> *From:* Alan Gates <alanfga...@gmail.com> >>>> *Sent:* Friday, June 19, 2015 11:44 AM >>>> *To:* dev@hive.apache.org >>>> *Subject:* Re: [VOTE] Apache Hive 1.2.1 Release Candidate 0 >>>> >>>> +1. Checked signatures, looked for binary files, compiled the code, and >>>> ran a rat check. >>>> >>>> Alan. >>>> >>>> Sushanth Sowmyan <khorg...@gmail.com> >>>> June 19, 2015 at 2:44 >>>> Hi Folks, >>>> >>>> It's been a month since 1.2.0, and I promised to do a stabilization >>>> 1.2.1 release, and this is it. A large number of patches have been >>>> applied since 1.2.0, and major known issues have been cleared/fixed. A >>>> few jiras were deferred out to 1.3/2.0 as not being ready to commit >>>> into 1.2.1 at this time. More details are available here : >>>> https://cwiki.apache.org/confluence/display/Hive/Hive+1.2+Release+Status >>>> >>>> Apache Hive 1.2.1 Release Candidate 0 is available here: >>>> >>>> https://people.apache.org/~khorgath/releases/1.2.1_RC0/artifacts/ >>>> >>>> My public key used for signing is as available from the hive >>>> committers key list : http://www.apache.org/dist/hive/KEYS >>>> >>>> Maven artifacts are available here: >>>> https://repository.apache.org/content/repositories/orgapachehive-1040/ >>>> >>>> Source tag for RC0 is up on the apache git repo as tag >>>> "release-1.2.1-rc0" (Browseable view over at >>>> >>>> https://git-wip-us.apache.org/repos/asf?p=hive.git;a=tag;h=0f6ee99efc911cbc1566f9bbbc63a51600302703 >>>> ) >>>> >>>> Voting will conclude in 72 hours. >>>> >>>> Hive PMC Members: Please test and vote. >>>> >>>> Thanks, >>>> -Sushanth >>>> >>>> >> >> >> >> -- >> Nothing better than when appreciated for hard work. >> -Mark
