On 18/02/2014 16:33, Gary Gregory wrote: > On Tue, Feb 18, 2014 at 4:09 AM, Mark Thomas <ma...@apache.org> wrote: > >> On 18/02/2014 05:01, Gary Gregory wrote: >>> Since you'll reroll the RC to fix the release notes for the version, you >>> might has well update to commons-parent 33 to pick up the new skin. >> >> Why do I need to reroll the RC to fix the release notes? > > > Because the RN file is part of the release, specifically, the source zip, > which is the primary artifact that the ASF releases.
What you appear to have missed is that what you were looking at was the 2.1 release notes not the 2.2 release notes. The 2.1 release notes were left over in dist/dev from the 2.1 release and as I didn't do an svn up before I added the 2.2 binaries and source I didn't realise that the release notes needed to be added to /dist. I fixed that by removing the 2.1 release notes and adding the 2.2 ones. > The tag should reflect what we publish for a given RC. The tag for the 2.2 > RC will be a copy of the tag for the RC that was voted on and passed. The release notes currently in dist/dev are exactly the same as those in the 2.2 tag. > That tag should include the release notes with the label "2.2", not "2.1". > Hence the request to have it all in sync. It's not the first time that a > new RC would include a fix for the release notes. Did you even look the the release notes in the 2.2 tag? They have the 2.2 label. http://svn.apache.org/viewvc/commons/proper/pool/tags/POOL_2_2_RC1/RELEASE-NOTES.txt?view=annotate Mark --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
