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 Ryaboy <dvrya...@gmail.com> wrote: > 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 < > prkommire...@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 > > >
