Release Checklist

For each new release the following tasks should be performed.

Code Quality

• Check for compiler warnings.
• Check for missing Javadoc.
• Run JUnit tests.
• Run findbugs.

Documentation

• Adjust user documentation to new features, update included screen shots.
• Finalize change log.

Build and Distribution

• Create SVN tag.
• Run Maven build with mvn clean install in the com.mountainminds.eclemma.build project as working directory. Also set the following options for bundle signing: jarsigner.keystore (path to JKS file), jarsigner.alias (mtnminds), jarsigner.storepass (keystore password), jarsigner.tsa (https://timestamp.geotrust.com/tsa), jarsigner.tsacert (mtnminds)
• Upload update site to Amazon S3 bucket for update.eclemma.org, adjust ACL for public read access.
• Rename zipped updates site (site_assembly.zip) to eclemma-x.y.z.zip and upload to SourceForge file release system.
• Adjust default SF download to new eclemma-x.y.z.zip file.
• Adjust version in page template for www.eclemma.org.
• Adjust eclemmasite/updatesite.sh to point to the new tag to fetch the correct version of user documentation.
• Publish www.eclemma.org by running eclemmasite/updatesite.sh.
• Increment plug-in's version numbers (MANIFEST.MF and pom.xml).
• Create SVN repository backup.

Support

• Close bugs and feature requests resolved by the new release.
• Add new group for the released version in the bug tracker.
• Update version information on marketplace.eclipse.org.