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/~prk
Release notes refer to CHANGES.txt which is inside a gzip. That seems less
than idea. Can we make CHANGES.txt available in the release directory for
future releases?
On Mon, Apr 7, 2014 at 1:22 PM, Prashant Kommireddi wrote:
> I have created a candidate build for Pig 0.12.1. This is a maintenan
Makes sense. We can make a note of that here
https://cwiki.apache.org/confluence/display/PIG/HowToRelease and do that
for 0.13.
I can include CHANGES.txt in the release directory now, that should not
require rolling a new RC. Would you like me to do that?
On Mon, Apr 7, 2014 at 2:58 PM, Dmitriy
.. ideal, I mean.
Here's the CHANGES link for those who are interested:
https://svn.apache.org/viewvc/pig/branches/branch-0.12/CHANGES.txt?revision=1585023&view=markup
Overall looks good to me. +1.
On Mon, Apr 7, 2014 at 2:58 PM, Dmitriy Ryaboy wrote:
> Release notes refer to CHANGES.txt whic
Issue Subscription
Filter: PIG patch available (18 issues)
Subscriber: pigdaily
Key Summary
PIG-3868Fix Iterator_1 e2e test on windows
https://issues.apache.org/jira/browse/PIG-3868
PIG-3867Added hadoop home to build classpath for build pig with unit test
on windows
