The following is a step-by-step procedure for releasing a new version of Google-Gson. - Mark all bugs as fixed for the release
- Ensure all changelists are code-reviewed and have +1
- Update the version tag in pom.xml
- Perform the following Maven commands, in order:
- mvn clean
- mvn package source:jar javadoc:jar assembly:assembly
- Navigate to target/dist and perform a sanity check on the zip bundle:
- unzip zip file
- jar tvf on the jar files and verify the proper files are in the jars
- Upload the zip bundle to the code.google.com/p/google-gson site (label this upload as "Featured")
- Deprecate old Gson version (click on version label and set the "Featured" label to "Deprecated")
- Copy generated JavaDocs from target/apidocs to trunk/gson/docs/javadocs
- Set the svn properties to the valid mime-types:
- find docs -name "*.html" | xargs svn propset svn:mime-type text/html
- find docs -name "*.gif" | xargs svn propset svn:mime-type image/gif
- Commit the JavaDoc changes into the repository
- Run mvn deploy in trunk/gson directory
- cd ../../mavenrepo/com/google/code/gson/gson/
- svn add 1.2.3
- svn commit (add the local maven repository to the googlecode.com)
- Tag the current release from trunk/gson
- mvn clean
- cd ../..
- svn copy trunk/gson tags/1.2.3
- svn commit tags -m "Release 1.2.3"
- Update the "API" link on the code.google.com home page to point to the newly tagged JavaDoc
- Update the version in the "Using Gson with Maven2" sites page
- Update Gson Roadmap to move the release down under the "Released section". Also, look at all bugs that were fixed and add a few lines describing what changed in the release.
- Create a post on the Gson Discussion Forum
|