Sounds good. Here is the approach I usually take when doing gs/gt releases:
1) Give a heads up to the gt list for release 2) Tag geotools release 3) Build and test geoserver release 4) Fix any geotools issues on the tag, back porting of course any fixes to the main branches 5) Finish off the geotools release And it works relatively well. -Justin Arne Kepp wrote: > Hi, > > we're starting the release train for GeoServer 1.7.4 and would like to > tag 2.5.6 soon if nobody has any objections. Based on the subversion > logs, Simone and Christian are the only ones actively committing on > 2.5.x these days and I have spoken to both of them. > > Simone said he would be ready later today. > > Christian would like to get IBM SDK compatibility patches in soon > (GEOT-2450, 2451, 2452, 2453 and others) so that GeoServer can run on > IBM SDKs as well. I sympathize strongly now that Oracle is calling the > shots, but I guess we should try to get those patches into the next release? > > Andrea, Gabriel or Justin will do the actual tagging and GT release, > since I am not a GT committer. > > -Arne > -- Justin Deoliveira OpenGeo - http://opengeo.org Enterprise support for open source geospatial. ------------------------------------------------------------------------------ Stay on top of everything new and different, both inside and around Java (TM) technology - register by April 22, and save $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco. 300 plus technical and hands-on sessions. Register today. Use priority code J9JMT32. http://p.sf.net/sfu/p _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
