pig-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Thejas Nair <the...@hortonworks.com>
Subject Re: [VOTE] Release Pig 0.12.1 (Candidate 0)
Date Sat, 12 Apr 2014 00:21:07 GMT
I have updated the wiki for this.
I have a post-release section where the version in number gets updated
to the next version.
https://cwiki.apache.org/confluence/pages/diffpagesbyversion.action?pageId=26120105&selectedPageVersions=27&selectedPageVersions=26


On Fri, Apr 11, 2014 at 11:57 AM, Daniel Dai <daijy@hortonworks.com> wrote:
> This is on our release document and we do follow in prior releases. It
> does not seems to be an Apache convention. I don't know the motivation
> of this, but if it is confusing enough, it might be better to change
> in next release.
>
> On Fri, Apr 11, 2014 at 11:17 AM, Prashant Kommireddi
> <prash1784@gmail.com> wrote:
>> Thanks Thejas. This actually came up during 0.12.0 RC as well and this is
>> Daniel's reply. I do agree with you on having pig.version in build.xml
>> reflect the current build rather than the next one. But I'm not aware of
>> what the Apache convention is, or what other projects are doing. You guys
>> know better :)
>>
>> *"Hi, Mark,*
>>
>>
>>
>>
>>
>> *Thanks for reviewing. "-SNAPSHOT" is intentional according to
>> "https://cwiki.apache.org/confluence/display/PIG/HowToRelease
>> <https://cwiki.apache.org/confluence/display/PIG/HowToRelease>". When
>> userbuild the release, the version will be {next
>> version}-SNAPSHOT.Thanks,Daniel"*
>>
>>
>> On Fri, Apr 11, 2014 at 10:45 AM, Thejas Nair <thejas@hortonworks.com>wrote:
>>
>>> Here is my late +1.
>>> Checked the md5 and asc keys.
>>> Checked release notes, CHANGES.txt.
>>> Build from source tar, tried some local queries. Checked output of
>>> version command (pig -version)
>>> The output of version command in binary is accurate.
>>>
>>> However, in case of source tar, when I build using just "ant" (without
>>> -Dversion..") , the version shows up as
>>> Apache Pig version 0.12.2-SNAPSHOT . I don't think this issue warrants a
>>> new RC.
>>> I think we should update the release instructions to change the
>>> version in build.xml to appropriate release version before tagging svn
>>> (and create tar using this tagged version), and then increment the
>>> version number in the next commit. If people agree, I can update the
>>> instructions in wiki.
>>>
>>>
>>> On Fri, Apr 11, 2014 at 1:54 AM, Prashant Kommireddi
>>> <prash1784@gmail.com> wrote:
>>> > The release vote passes with 4 +1s (4 binding votes), and no -1s.
>>> >
>>> > +1s (binding)
>>> > Dmitriy Ryaboy
>>> > Daniel Dai
>>> > Cheolsoo Park
>>> > Alan Gates
>>> >
>>> > +1s (non-binding)
>>> > None
>>> >
>>> > -1s
>>> > None
>>> >
>>> > Thanks Daniel for pointing out the missing pig-0.12.1.tar.gz.asc file. I
>>> > have added it to the RC.
>>> >
>>> > I will proceed with the release process.
>>> >
>>> > Thanks,
>>> > Prashant
>>> >
>>> >
>>> > On Thu, Apr 10, 2014 at 10:54 AM, Alan Gates <gates@hortonworks.com>
>>> wrote:
>>> >
>>> >> +1
>>> >>
>>> >> Reviewed LICENSE, NOTICE, RELEASE_NOTES, and README.  Built, built
>>> >> piggybank and ran tests, ran a local smoke test.
>>> >>
>>> >> Alan.
>>> >>
>>> >> On Apr 7, 2014, at 1:22 PM, Prashant Kommireddi <
>>> prkommireddi@apache.org>
>>> >> wrote:
>>> >>
>>> >> > I have created a candidate build for Pig 0.12.1. This is a maintenance
>>> >> > release to Pig 0.12.0 with a few critical bug fixes.
>>> >> >
>>> >> > Keys used to sign the release are available at
>>> >> > http://svn.apache.org/viewvc/pig/trunk/KEYS?view=markup.
>>> >> >
>>> >> > Please download, test, and try it out:
>>> >> >
>>> >> > http://people.apache.org/~prkommireddi/pig-0.12.1-candidate-0/
>>> >> >
>>> >> >
>>> >> > Release notes and the rat report are available from the same location.
>>> >> >
>>> >> >
>>> >> > List of issues fixed in this release
>>> >> >
>>> >> >
>>> >>
>>> http://svn.apache.org/viewvc/pig/branches/branch-0.12/CHANGES.txt?view=markup
>>> >> >
>>> >> > Should we release this? Vote closes EOD this Thursday, April 10th.
>>> >> >
>>> >> > -Prashant
>>> >>
>>> >>
>>> >> --
>>> >> 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.
>>>
>
> --
> 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.

Mime
View raw message