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

+1 .
Checked checksum and signatures of all 3 packages. Ran simple queries in
MR and local modes using tar package on unsecure cluster, and rpm
package on secure cluster.

Thanks,
Thejas

On 4/20/12 12:39 AM, Daniel Dai 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

+1

Checked checksums and unit tests (test-commit) for both Pig and Piggybank.
Only failure was the TestPigServer error already noted.

On Tue, Apr 24, 2012 at 3:06 PM, Thejas Nair <[EMAIL PROTECTED]> wrote:

> +1 .
> Checked checksum and signatures of all 3 packages. Ran simple queries in
> MR and local modes using tar package on unsecure cluster, and rpm package
> on secure cluster.
>
> Thanks,
> Thejas
>
>
> On 4/20/12 12:39 AM, Daniel Dai 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<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/<http://people.apache.org/~daijy/pig-0.10.0-candidate-0/>
>>
>> Should we release this? Vote closes on next Tuesday, Apr 24th.
>>
>> Daniel
>>
>
>

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 <[EMAIL PROTECTED]> 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
>

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
<[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>

+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
> next release at this stage unless it is a critical one.
>
> Thanks,
> Daniel
>
> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>

Uh, actually, one of the test-commit tests failed in my environment.

In TestPigServer:

Testcase: testDefaultPigProperties took 0.033 sec
        Caused an ERROR
null
java.lang.NullPointerException
        at org.apache.pig.test.TestPigServer.testDefaultPigProperties(TestPigServer.java:895)

Something about my environment?

D
On Mon, 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
>> next release at this stage unless it is a critical one.
>>
>> Thanks,
>> Daniel
>>
>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>

I have a wrapper script to switch between Pig versions and clusters.

export PIG_HOME=$HOME/tools/Linux/hadoop/pig-$PIG_VERSION
export JAVA_HOME=$HOME/tools/Linux/jdk/jdk$JAVA_VERSION/
export PIG_CLASSPATH=$HOME/apps/gridforce/main/hadoop/conf/$HADOOP_CLUSTER

HADOOP_CLUSTER contains the hadoop configs (endpoints) for the cluster I
want to point to.

And then I do this to start pig.

$PIG_HOME/bin/pig

This works with previous versions pig-0.8.0 and pig-0.9.1. However,
pig-0.10.0 fails to pick up the right classpath.

$ ./pig.sh
 ..
.....
......
2012-04-23 20:42:35,340 [main] INFO
org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - Connecting
to hadoop file system at: file:///

Is this something with my script, or may be the new version (0.10.0)?

-Prashant
On Mon, Apr 23, 2012 at 8:30 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:

> Uh, actually, one of the test-commit tests failed in my environment.
>
> In TestPigServer:
>
> Testcase: testDefaultPigProperties took 0.033 sec
>        Caused an ERROR
> null
> java.lang.NullPointerException
>        at
> org.apache.pig.test.TestPigServer.testDefaultPigProperties(TestPigServer.java:895)
>
> Something about my environment?
>
> D
>
>
> On Mon, 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
> >> next release at this stage unless it is a critical one.
> >>
> >> Thanks,
> >> Daniel
> >>
> >> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
> >> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
> 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
> >>>>
>

pig.sh understands the arguments below -- try setting HADOOP_CONF_DIR?

# Environment Variables
#
#     JAVA_HOME                The java implementation to use.
Overrides JAVA_HOME.
#
#     PIG_CLASSPATH Extra Java CLASSPATH entries.
#
#     HADOOP_HOME/HADOOP_PREFIX     Environment
HADOOP_HOME/HADOOP_PREFIX(0.20.205)
#
#     HADOOP_CONF_DIR     Hadoop conf dir
#
#     PIG_HEAPSIZE    The maximum amount of heap to use, in MB.
#                                        Default is 1000.
#
#     PIG_OPTS            Extra Java runtime options.
#
#     PIG_CONF_DIR    Alternate conf dir. Default is ${PIG_HOME}/conf.
#
#     HBASE_CONF_DIR - Optionally, the HBase configuration to run against
#                      when using HBaseStorage

On Mon, Apr 23, 2012 at 8:45 PM, Prashant Kommireddi
<[EMAIL PROTECTED]> wrote:
> I have a wrapper script to switch between Pig versions and clusters.
>
> export PIG_HOME=$HOME/tools/Linux/hadoop/pig-$PIG_VERSION
> export JAVA_HOME=$HOME/tools/Linux/jdk/jdk$JAVA_VERSION/
> export PIG_CLASSPATH=$HOME/apps/gridforce/main/hadoop/conf/$HADOOP_CLUSTER
>
> HADOOP_CLUSTER contains the hadoop configs (endpoints) for the cluster I
> want to point to.
>
> And then I do this to start pig.
>
> $PIG_HOME/bin/pig
>
> This works with previous versions pig-0.8.0 and pig-0.9.1. However,
> pig-0.10.0 fails to pick up the right classpath.
>
> $ ./pig.sh
>  ..
> .....
> ......
> 2012-04-23 20:42:35,340 [main] INFO
> org.apache.pig.backend.hadoop.executionengine.HExecutionEngine - Connecting
> to hadoop file system at: file:///
>
> Is this something with my script, or may be the new version (0.10.0)?
>
> -Prashant
>
>
> On Mon, Apr 23, 2012 at 8:30 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
>> Uh, actually, one of the test-commit tests failed in my environment.
>>
>> In TestPigServer:
>>
>> Testcase: testDefaultPigProperties took 0.033 sec
>>        Caused an ERROR
>> null
>> java.lang.NullPointerException
>>        at
>> org.apache.pig.test.TestPigServer.testDefaultPigProperties(TestPigServer.java:895)
>>
>> Something about my environment?
>>
>> D
>>
>>
>> On Mon, 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
>> >> next release at this stage unless it is a critical one.
>> >>
>> >> Thanks,
>> >> Daniel
>> >>
>> >> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>> >> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
>> 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
>> >>>>
>>

Thanks Dmitriy, that works. But I am wondering why the behavior is
different from the previous versions.

Difference I see in bin/pig is (0.10.0 vs 0.9.1)

> # add HADOOP_CONF_DIR
> if [ "$HADOOP_CONF_DIR" != "" ]; then
>     CLASSPATH=${CLASSPATH}:${HADOOP_CONF_DIR}
> fi

AFAIK, this should not affect it - all it's doing is adding the conf dir to
the classpath which I was doing earlier through PIG_CLASSPATH in my wrapper
script.

The issue here is that certain properties are not same between client
machine and remote cluster, for eg JAVA_HOME. Since pig is client side it
made sense for Pig to not pick up any cluster properties from
"hadoop-env.sh". I am not sure what the change here is that's now causing
it to be picked up.

On Mon, Apr 23, 2012 at 9:14 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:

> pig.sh understands the arguments below -- try setting HADOOP_CONF_DIR?
>
> # Environment Variables
> #
> #     JAVA_HOME                The java implementation to use.
> Overrides JAVA_HOME.
> #
> #     PIG_CLASSPATH Extra Java CLASSPATH entries.
> #
> #     HADOOP_HOME/HADOOP_PREFIX     Environment
> HADOOP_HOME/HADOOP_PREFIX(0.20.205)
> #
> #     HADOOP_CONF_DIR     Hadoop conf dir
> #
> #     PIG_HEAPSIZE    The maximum amount of heap to use, in MB.
> #                                        Default is 1000.
> #
> #     PIG_OPTS            Extra Java runtime options.
> #
> #     PIG_CONF_DIR    Alternate conf dir. Default is ${PIG_HOME}/conf.
> #
> #     HBASE_CONF_DIR - Optionally, the HBase configuration to run against
> #                      when using HBaseStorage
>
>
>
> On Mon, Apr 23, 2012 at 8:45 PM, Prashant Kommireddi
> <[EMAIL PROTECTED]> wrote:
> > I have a wrapper script to switch between Pig versions and clusters.
> >
> > export PIG_HOME=$HOME/tools/Linux/hadoop/pig-$PIG_VERSION
> > export JAVA_HOME=$HOME/tools/Linux/jdk/jdk$JAVA_VERSION/
> > export
> PIG_CLASSPATH=$HOME/apps/gridforce/main/hadoop/conf/$HADOOP_CLUSTER
> >
> > HADOOP_CLUSTER contains the hadoop configs (endpoints) for the cluster I
> > want to point to.
> >
> > And then I do this to start pig.
> >
> > $PIG_HOME/bin/pig
> >
> > This works with previous versions pig-0.8.0 and pig-0.9.1. However,
> > pig-0.10.0 fails to pick up the right classpath.
> >
> > $ ./pig.sh
> >  ..
> > .....
> > ......
> > 2012-04-23 20:42:35,340 [main] INFO
> > org.apache.pig.backend.hadoop.executionengine.HExecutionEngine -
> Connecting
> > to hadoop file system at: file:///
> >
> > Is this something with my script, or may be the new version (0.10.0)?
> >
> > -Prashant
> >
> >
> > On Mon, Apr 23, 2012 at 8:30 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
> wrote:
> >
> >> Uh, actually, one of the test-commit tests failed in my environment.
> >>
> >> In TestPigServer:
> >>
> >> Testcase: testDefaultPigProperties took 0.033 sec
> >>        Caused an ERROR
> >> null
> >> java.lang.NullPointerException
> >>        at
> >>
> org.apache.pig.test.TestPigServer.testDefaultPigProperties(TestPigServer.java:895)
> >>
> >> Something about my environment?
> >>
> >> D
> >>
> >>
> >> On Mon, 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
> >> >> next release at this stage unless it is a critical one.
> >> >>
> >> >> Thanks,
> >> >> Daniel
> >> >>
> >> >> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
> >> >> <[EMAIL PROTECTED]> wrote:
> >> >>> Hi Daniel,
> >> >>>
> >> >>> What is required other than running the regular tests for testing

Do you have HADOOP_HOME? Both HADOOP_CONF_DIR/PIG_CLASSPATH should
work, can you use bin/pig -secretDebugCmd to check hadoop command
line?

On Mon, Apr 23, 2012 at 11:32 PM, Prashant Kommireddi
<[EMAIL PROTECTED]> wrote:
> Thanks Dmitriy, that works. But I am wondering why the behavior is
> different from the previous versions.
>
> Difference I see in bin/pig is (0.10.0 vs 0.9.1)
>
>> # add HADOOP_CONF_DIR
>> if [ "$HADOOP_CONF_DIR" != "" ]; then
>>     CLASSPATH=${CLASSPATH}:${HADOOP_CONF_DIR}
>> fi
>
> AFAIK, this should not affect it - all it's doing is adding the conf dir to
> the classpath which I was doing earlier through PIG_CLASSPATH in my wrapper
> script.
>
> The issue here is that certain properties are not same between client
> machine and remote cluster, for eg JAVA_HOME. Since pig is client side it
> made sense for Pig to not pick up any cluster properties from
> "hadoop-env.sh". I am not sure what the change here is that's now causing
> it to be picked up.
>
>
>
> On Mon, Apr 23, 2012 at 9:14 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
>
>> pig.sh understands the arguments below -- try setting HADOOP_CONF_DIR?
>>
>> # Environment Variables
>> #
>> #     JAVA_HOME                The java implementation to use.
>> Overrides JAVA_HOME.
>> #
>> #     PIG_CLASSPATH Extra Java CLASSPATH entries.
>> #
>> #     HADOOP_HOME/HADOOP_PREFIX     Environment
>> HADOOP_HOME/HADOOP_PREFIX(0.20.205)
>> #
>> #     HADOOP_CONF_DIR     Hadoop conf dir
>> #
>> #     PIG_HEAPSIZE    The maximum amount of heap to use, in MB.
>> #                                        Default is 1000.
>> #
>> #     PIG_OPTS            Extra Java runtime options.
>> #
>> #     PIG_CONF_DIR    Alternate conf dir. Default is ${PIG_HOME}/conf.
>> #
>> #     HBASE_CONF_DIR - Optionally, the HBase configuration to run against
>> #                      when using HBaseStorage
>>
>>
>>
>> On Mon, Apr 23, 2012 at 8:45 PM, Prashant Kommireddi
>> <[EMAIL PROTECTED]> wrote:
>> > I have a wrapper script to switch between Pig versions and clusters.
>> >
>> > export PIG_HOME=$HOME/tools/Linux/hadoop/pig-$PIG_VERSION
>> > export JAVA_HOME=$HOME/tools/Linux/jdk/jdk$JAVA_VERSION/
>> > export
>> PIG_CLASSPATH=$HOME/apps/gridforce/main/hadoop/conf/$HADOOP_CLUSTER
>> >
>> > HADOOP_CLUSTER contains the hadoop configs (endpoints) for the cluster I
>> > want to point to.
>> >
>> > And then I do this to start pig.
>> >
>> > $PIG_HOME/bin/pig
>> >
>> > This works with previous versions pig-0.8.0 and pig-0.9.1. However,
>> > pig-0.10.0 fails to pick up the right classpath.
>> >
>> > $ ./pig.sh
>> >  ..
>> > .....
>> > ......
>> > 2012-04-23 20:42:35,340 [main] INFO
>> > org.apache.pig.backend.hadoop.executionengine.HExecutionEngine -
>> Connecting
>> > to hadoop file system at: file:///
>> >
>> > Is this something with my script, or may be the new version (0.10.0)?
>> >
>> > -Prashant
>> >
>> >
>> > On Mon, Apr 23, 2012 at 8:30 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]>
>> wrote:
>> >
>> >> Uh, actually, one of the test-commit tests failed in my environment.
>> >>
>> >> In TestPigServer:
>> >>
>> >> Testcase: testDefaultPigProperties took 0.033 sec
>> >>        Caused an ERROR
>> >> null
>> >> java.lang.NullPointerException
>> >>        at
>> >>
>> org.apache.pig.test.TestPigServer.testDefaultPigProperties(TestPigServer.java:895)
>> >>
>> >> Something about my environment?
>> >>
>> >> D
>> >>
>> >>
>> >> On Mon, 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,

I known what happen. There is a difference in release tar ball vs svn,
conf/pig-default.properties is merged into pig-X.X.X-withouthadoop.jar
in the release. However, when running unit test, Pig will build a
pig-withouthadoop without such file, thus TestPigServer fail. This
happens in the previous releases as well. We shall fix it in future
releases.

On Mon, Apr 23, 2012 at 8:30 PM, Dmitriy Ryaboy <[EMAIL PROTECTED]> wrote:
> Uh, actually, one of the test-commit tests failed in my environment.
>
> In TestPigServer:
>
> Testcase: testDefaultPigProperties took 0.033 sec
>        Caused an ERROR
> null
> java.lang.NullPointerException
>        at org.apache.pig.test.TestPigServer.testDefaultPigProperties(TestPigServer.java:895)
>
> Something about my environment?
>
> D
>
>
> On Mon, 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
>>> next release at this stage unless it is a critical one.
>>>
>>> Thanks,
>>> Daniel
>>>
>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>>

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
>> next release at this stage unless it is a critical one.
>>
>> Thanks,
>> Daniel
>>
>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>

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
>>> next release at this stage unless it is a critical one.
>>>
>>> Thanks,
>>> Daniel
>>>
>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>>

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
>>>> next release at this stage unless it is a critical one.
>>>>
>>>> Thanks,
>>>> Daniel
>>>>
>>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>>>

Since that's not a regression, this shouldn't block 0.10.0 (but we
should fix it).

Protip: if you attach a patch as a file , click the "grant apache
license" while uploading, and then hit "patch available", it will show
up on our filters as an issue that has an available patch, and this
will be more likely to get committed in a reasonable timeframe..

D

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
>>>>> next release at this stage unless it is a critical one.
>>>>>
>>>>> Thanks,
>>>>> Daniel
>>>>>
>>>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]> 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
>>>>>>>

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
> >>>> next release at this stage unless it is a critical one.
> >>>>
> >>>> Thanks,
> >>>> Daniel
> >>>>
> >>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
> >>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
> 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
[EMAIL PROTECTED] going forward.*

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
>> >>>> next release at this stage unless it is a critical one.
>> >>>>
>> >>>> Thanks,
>> >>>> Daniel
>> >>>>
>> >>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>> >>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
>> 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
> [EMAIL PROTECTED] going forward.*

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
>>>>>>> next release at this stage unless it is a critical one.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Daniel
>>>>>>>
>>>>>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>>>>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
>>> 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
>> [EMAIL PROTECTED] going forward.*

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
>>>>>>>> next release at this stage unless it is a critical one.
>>>>>>>>
>>>>>>>> Thanks,
>>>>>>>> Daniel
>>>>>>>>
>>>>>>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>>>>>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
>>>> 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
>>> [EMAIL PROTECTED] going forward.*
>

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
> >>>>>>>> next release at this stage unless it is a critical one.
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>> Daniel
> >>>>>>>>
> >>>>>>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
> >>>>>>>> <[EMAIL PROTECTED]> 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 <
> [EMAIL PROTECTED]>
> >>>> 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.
> >>>>>>>>>>
> >>>>
Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

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
>> >>>>>>>> next release at this stage unless it is a critical one.
>> >>>>>>>>
>> >>>>>>>> Thanks,
>> >>>>>>>> Daniel
>> >>>>>>>>
>> >>>>>>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>> >>>>>>>> <[EMAIL PROTECTED]> 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 <

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
> >> >>>>>>>> next release at this stage unless it is a critical one.
> >> >>>>>>>>
> >> >>>>>>>> Thanks,
> >> >>>>>>>> Daniel
> >> >>>>>>>>
> >> >>>>>>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
> >> >>>>>>>> <[EMAIL PROTECTED]> wrote:
> >> >>>>>>>>> Hi Daniel,
> >> >>>>>>>>>
> >> >>>>>>>>> What is required other than running the regular tests for

Russell Jurney twitter.com/rjurney [EMAIL PROTECTED] datasyndrome.com

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
>> >

Thanks Daniel. Upgrade time!
On Apr 24, 2012, at 11:51 PM, Daniel Dai <[EMAIL PROTECTED]> wrote:

> 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,
>>>>>>

Ship it!
--
Gianmarco

On Wed, Apr 25, 2012 at 09:35, Prashant Kommireddi <[EMAIL PROTECTED]>wrote:

> Thanks Daniel. Upgrade time!
>
>
> On Apr 24, 2012, at 11:51 PM, Daniel Dai <[EMAIL PROTECTED]> wrote:
>
> > 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.
> >>>>>>

We should make JIRA tickets for all of the stuff that came up in this
thread and tag them against 0.10.1. nothing life threatening, but will
clean things up...

2012/4/25 Gianmarco De Francisci Morales <[EMAIL PROTECTED]>

> Ship it!
> --
> Gianmarco
>
>
>
> On Wed, Apr 25, 2012 at 09:35, Prashant Kommireddi <[EMAIL PROTECTED]
> >wrote:
>
> > Thanks Daniel. Upgrade time!
> >
> >
> > On Apr 24, 2012, at 11:51 PM, Daniel Dai <[EMAIL PROTECTED]> wrote:
> >
> > > 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.

wooh!

2012/4/25 Daniel Dai <[EMAIL PROTECTED]>

> 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]>

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 <[EMAIL PROTECTED]> 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
>>> >>>> next release at this stage unless it is a critical one.
>>> >>>>
>>> >>>> Thanks,
>>> >>>> Daniel
>>> >>>>
>>> >>>> On Sat, Apr 21, 2012 at 12:48 AM, Prashant Kommireddi
>>> >>>> <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]>
>>> 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
>> [EMAIL PROTECTED] going forward.*