[afp-renderer-developers] Release procedures
Brought to you by:
towny,
tumbarumba
From: Joe S. <jo...@ex...> - 2004-11-20 21:35:41
|
Just checked into CVS... the ant build now supports a "release" target, which should simplify building release. The following is a procedure/checklist which I think should be followed for an official release. This procedure uses version 1.1.0 as an example, and assumes a valid environment with CVSROOT, JAVA_HOME and ANT_HOME correctly defined. 1) Make sure CHANGES, README, etc are up to date. Edit build.properties to reflect the new release version, and check it into HEAD. dist.version = 1.1.0 dist.type = ... cvs ci -m "Release 1.1.0" build.properties 2) Tag the new release in CVS. cvs rtag -rHEAD AFP_RENDERER_1_1_0 afp-fop-src 3) Checkout a clean workspace using the tag and cd into it cvs co -rAFP_RENDERER_1_0_0 afp-fop-src cd afp-fop-src 4) Run the release target in ant. This should create a new file called afp-renderer-1.1.0.zip in the current directory. This is the file to be published. ant release 5) Publish the release using the sourceforge admin interface. 6) To avoid accidentally creating a new release of the same name, immediately bump up the build.properties version properties to the next incremental release and check in. dist.version = 1.1.1 dist.type = -dev ... cvs ci -m "Release 1.1.1-dev" build.properties I think that's about it. Thoughts? Comments? Cheers, Joe |