Just committed the release scripts.

On Tue, May 29, 2012 at 9:09 PM, Jody Garnett <jody.garnett@gmail.com> wrote:
Yeah, if you look at the patch it actually modifies the rename script so that on the main branch it is never modified. Basically adding a @VERSION@ placeholder.
Understood; we also need to update a few doc references (on the main branch) in anticipation of the release being a success.
Anyways, the scripts take this into account, i have just never ran them through a full trial to test the commit back but its the same pattern as GeoServer and I just cribbed the scripts from there and stripped them down.
So the example pom.xml files in docs/user/tutorials need to reflect the release version number; and the build/pom.xml and common.py also have a reference.

Hmm... ok. I thought this was all handled by rename.xml? If not that is fine, just need to know what files to change the version in. And on the main branches replace any version numbers that are there with the same @VERSION@ placeholder. Then we just need to update the release script to do the place with sed. 

Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.