Andrea Aime ha scritto: > so in order to release > GeoServer 1.6.3 we either have to: > * make sure no change in geotools occurred that affects GeoServer, and > thus we can still use the old gt2 release (very unlikely usually, > given that most bugs we fix for geoserver do really require a fix > in geotools, and sure for this release, since Gabriel has been doing > massive changes in the arcsde module that we need) > * a week before, issue a warning to geotools devel telling people > that we'll need to cut a release and out of which branch, basically > issuing the same warning as you did on geoserver-devel for geoserver > (if you have to commit anything, do it now or wait for the > next release).
Ah, one thing. The good procedure is not to release 2.4.x and then start releasing 1.6.x... that is, it's not unless you want to make the gt2 release twice. The first time I did the release, I first released gt2, and then started doing cite tests that showed a failure, which needed a fix in gt2. So I had to re-release it (pain!). The procedure is more like: * announce freeze on both projects * build both projects from a clean checkout (no local modifications) * run the cite tests, make sure we're ok * release gt2 * release geoserver Hope this helps Cheers Andrea ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
