Releasing

Overview

The following steps describe how to release dbUnit. While the Maven release plugin automates steps such as version change, commit, and deploy, dbUnit has manual file information update steps that are outside of its scope.

While the below steps do not use the Maven release plugin, you can use it by performing the manual file edits first then running the release plugin steps.

Release Steps

Update pom.xml
1. Set version to release version
2. Set project.build.outputTimestamp property to the release timestamp, typically today’s date with midnight time
3. Update japicmp-maven-plugin configuration
  1. Add reportSet for prior version to new version comparison
  2. Comment out reportSet comparison to latest snapshot until a new snapshot exists
Update site.xml
1. Add menu entry for japicmp prior version to new version comparison
2. Comment out comparison to latest snapshot until a new snapshot exists
Update changes.xml
1. Update release version
2. Set release date to today
Update index.xml
1. Add entry to release section; ensure correct links
Commit files "Prep release x.y.z"
Tag the commit
Push the commit
Build and deploy the release
```
mvnw clean
mvnw deploy -Prelease
```
Build and deploy the site
1. Build site:
```
mvnw site
```
2. Review site results for issues and correct as necessary
3. Publish: Commits to master automatically build the site and publish to GitHub pages.
  - Historical: Deploy to SourceForge; reference how-to: Deploying to sourceforge.net
```
ssh -t sf-username,dbunit@shell.sourceforge.net create
mvnw site:deploy
```
Generate Announcement Email
```
mvnw changes:announcement-generate -Dchanges.version=theNewVersion
```
Review and adjust the text as desired before using.
Email Users List
Post News on SourceForge
Prepare next release in SCM
1. Update pom.xml
  1. Update to SNAPSHOT version
  2. Update japicmp-maven-plugin configuration with comparison of latest release to new snapshot
2. Update index.xml with new SNAPSHOT entry
3. Update changes.xml with new SNAPSHOT entry