That was all my spot checks picked out. Next up ( in the manual procedure )
would be to build the artifacts. And either test the that the source code
artifact is complete, or upload it and send an email asking the community
to test.
Usually while I wait for those build I write up the blog post announcement
- you have access to the blog? Not sure what you want to say about this
release - perhaps 'last release from svn"?
--
Jody Garnett
On 28/06/2012, at 8:01 PM, "victor....@csiro.au" <victor....@csiro.au>
wrote:
Looks like my patch didn’t make it in time for the CITE test. Idid a dry
run and http://svn.osgeo.org/geotools/tags/8.0-RC2/docs/common.py now has
2012 instead of 2011.
http://gridlock.opengeo.org/geotools/release/8.0-RC2/
Please let me know if there are anything else required to be fixed. Thanks J
*Victor Tey *
Software Engineer
**
*From:* Jody Garnett [mailto:jody.garn...@gmail.com]
*Sent:* Thursday, 28 June 2012 1:48 PM
*To:* Tey, Victor (CESRE, Kensington)
*Cc:* andrea.a...@geo-solutions.it; jdeol...@opengeo.org;
geotools-devel@lists.sourceforge.net
*Subject:* Re: [Geotools-devel] Releasing GT 8.0 RC2
The result could have been cache. Try refreshing
Good idea - checking:
5) http://svn.osgeo.org/geotools/tags/8.0-RC2/docs/common.py
- 8.0-RC1
- 2011, GeoTools
2011, GeoTools is still there - something to fix on trunk as well.
Jody
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
