When make the release, we will pass -Dversion=, but don't change
build.xml. So if we build from the release tall ball, we will get a
SNAPSHOT.jar. That's true for all previous pig release and hadoop
release.
On Tue, Apr 24, 2012 at 3:16 PM, Dmitriy Ryaboy <dvrya...@gmail.com> wrote:
> That's a good catch.
>
> We shouldn't officially publish a "SNAPSHOT" build...
>
> Or does that get fixed only when you officially publish? Wouldn't the
> signature change?
>
> D
>
> On Tue, Apr 24, 2012 at 9:39 AM, Bill Graham <billgra...@gmail.com> wrote:
>> I'm working on getting through the unit tests, but should SNAPSHOT still be
>> in the version?
>>
>> $ grep SNAPSHOT build.xml
>> <property name="version" value="${pig.version}-SNAPSHOT" />
>>
>>
>> On Tue, Apr 24, 2012 at 8:47 AM, Joseph Adler <joseph.ad...@gmail.com>wrote:
>>
>>> Can you guys please fix https://issues.apache.org/jira/browse/PIG-2266
>>>
>>> Without that, I can guarantee that AvroStorage will fail on large files.
>>>
>>> On Mon, Apr 23, 2012 at 8:07 PM, Joseph Adler <joseph.ad...@me.com> wrote:
>>> > I will do it tomorrow on one of my workflows. Could take some trial and
>>> error to get it working.
>>> >
>>> > -- Joe
>>> >
>>> > On Apr 23, 2012, at 6:53 PM, Russell Jurney <russell.jur...@gmail.com>
>>> wrote:
>>> >
>>> >> Can someone from LinkedIn try this release candidate? It may break
>>> >> your AvroStorage, so that would be good to know.
>>> >>
>>> >> Russell Jurney http://datasyndrome.com
>>> >>
>>> >> On Apr 23, 2012, at 6:36 PM, Dmitriy Ryaboy <dvrya...@gmail.com> wrote:
>>> >>
>>> >>> +1
>>> >>>
>>> >>>
>>> >>> Verified several jobs using Elephant-Bird loaders.
>>> >>> Tested correctness with pig.exec.mapPartAgg both true and false.
>>> >>> Verified license.
>>> >>> Verified release notes.
>>> >>> Ran test-commit
>>> >>>
>>> >>> D
>>> >>>
>>> >>> On Sat, Apr 21, 2012 at 12:27 PM, Daniel Dai <da...@hortonworks.com>
>>> wrote:
>>> >>>> We should do sanity check of the package, such as unit tests, e2e
>>> >>>> tests, piggybank tests, package integrity, package signature, license,
>>> >>>> etc. However, if we find a new bug, usually we will push it to the
>>> >>>> next release at this stage unless it is a critical one.
>>> >>>>
>>> >>>> Thanks,
>>> >>>> Daniel
>>> >>>>
>>> >>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>> >>>> <prash1...@gmail.com> wrote:
>>> >>>>> Hi Daniel,
>>> >>>>>
>>> >>>>> What is required other than running the regular tests for testing
>>> release
>>> >>>>> candidate? I can think of running a few existing scripts against
>>> candidate
>>> >>>>> build and making sure outputs look fine.
>>> >>>>>
>>> >>>>> Thanks,
>>> >>>>> Prashant
>>> >>>>>
>>> >>>>> On Fri, Apr 20, 2012 at 12:39 AM, Daniel Dai <da...@hortonworks.com>
>>> wrote:
>>> >>>>>
>>> >>>>>> Hi,
>>> >>>>>>
>>> >>>>>> I have created a candidate build for Pig 0.10.0.
>>> >>>>>>
>>> >>>>>> 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/~daijy/pig-0.10.0-candidate-0/
>>> >>>>>>
>>> >>>>>> Should we release this? Vote closes on next Tuesday, Apr 24th.
>>> >>>>>>
>>> >>>>>> Daniel
>>> >>>>>>
>>>
>>
>>
>>
>> --
>> *Note that I'm no longer using my Yahoo! email address. Please email me at
>> billgra...@gmail.com going forward.*
