Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Threaded View
Pig >> mail # dev >> [VOTE] Release Pig 0.10.0 (candidate 0)


Copy link to this message
-
Re: [VOTE] Release Pig 0.10.0 (candidate 0)
With 4 +1 (Dmitriy, Thejas, Bill, Daniel) and no -1, the vote pass. I
will go ahead and release 0.10.0.

Thanks,
Daniel

On Tue, Apr 24, 2012 at 5:11 PM, Russell Jurney
<[EMAIL PROTECTED]> wrote:
> Ok, .10.1 is fine.
>
> On Tue, Apr 24, 2012 at 5:08 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
>> We can put it into 0.10.1.
>>
>> IMO the only thing that should block a release, especially one that's
>> been pending for so long, are major regressions (efficiency or
>> functionality) or correctness issues. Things that didn't work before
>> still not working is unfortunate but not a blocker.
>>
>> (Also: this is why we should disconnect piggybank from pig releases...)
>>
>> D
>>
>> On Tue, Apr 24, 2012 at 4:58 PM, Russell Jurney
>> <[EMAIL PROTECTED]> wrote:
>> > This bug was never fixed, and I'm assured AvroStrorage fails on large
>> files
>> > in a production context. Any chance I can write tests for the patch in
>> > comments and get it in 0.10?
>> >
>> > https://issues.apache.org/jira/browse/PIG-2266
>> >
>> > On Tue, Apr 24, 2012 at 4:01 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>> wrote:
>> >
>> >> Heh. Ok my +1 stands.
>> >>
>> >> On Tue, Apr 24, 2012 at 3:25 PM, Alan Gates <[EMAIL PROTECTED]>
>> wrote:
>> >> > Oddly enough that's how we've always done the version numbering in the
>> >> build file, setting it up for the next version.  I agree we should
>> change
>> >> it, but since we've done it in every release since 0.1, I don't think we
>> >> should block 0.10 for it.  The change is to change the directions in
>> >> HowToRelease.
>> >> >
>> >> > Alan.
>> >> >
>> >> > On Apr 24, 2012, at 3:16 PM, Dmitriy Ryaboy 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 <[EMAIL PROTECTED]>
>> >> 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 <
>> [EMAIL PROTECTED]
>> >> >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 <[EMAIL PROTECTED]
>> >
>> >> 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 <
>> >> [EMAIL PROTECTED]>
>> >> >>>> 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 <[EMAIL PROTECTED]>
>> >> 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 <
>> >> [EMAIL PROTECTED]>
>> >> >>>> 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
>> >