Well, I already do that for handling the tagged releases, so it's not so hard to do it on 1.6.x as well. I'll add it to the release guide (which is slowly being made sane).
http://geoserver.org/display/GEOSDOC/7+Releasing Thanks, Mike Andrea Aime wrote: > Mike Pumphrey ha scritto: >> Should we be handling version numbers on branches differently? I too >> have gotten confused by this on a few occasions? Is there a Best >> Practice for this sort of thing? > > No, it's just that some would have to go into the i18n files > after each release and change the name to GeoServer 1.6.n+1-snapshot, > for example, after the current release, make it 1.6.5-snapshot or > 1.6.5-beta > > Cheers > Andrea > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel > > !DSPAM:4051,4832f1f7258941849620573! > ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
