Automation: Release

Release [comp] [version]

Current manual process consist of:

Jira:

• find smallest [comp]_x.x.x.next version in Jira
  • if any issues assigned to version are 'Resolved' we have something to release
• create new version [comp]_[version]
• create new issue with fix version [comp]_[version]: Prepare [comp] [version] Release
• update all 'Resolved' issues on [comp]_x.x.x.next to fixed version [version]

Maven:

• find current dev version x.x.x.Final-SNAPSHOT
• run maven release:prepare release:perform -DdevelopmentVersion=x.x.x-Final.SNAPSHOT -DreleaseVersion=[version] -DscmCommentPrefix=[JIRA_ISSUE]

(can we avoid nexus staging repos ?)

Jira:

• close all issues on [comp]_[version]
• mark [comp]_[version] version as Released

When it runs

We should expose the automated release dates in a calendar so people can easly see when a new release is expected. It could even work as a control center for us: Need a few more days for a specific feature to go in, just update by dragging the 'release event' over in gcal, woala.

Doing continues 'deployments' will give us a lot of small release notes, which adds a extra stress level for creating the 'release notes hightlights' blogs. We should make sure our Jiras are clear and descriptive and can be used directly in the release notes without the extra hightlights.

• Rewrite incoming issues to a positive spin e.g.
  • NullPointerException in.. -> Should be able to ..
  • can't configure xxx -> Add support for configuring xxxx
• Redo the Issues List in the Release notes to show Subject and Description (possible add a 'show details' to display the description)
• Possible add a feature to the Release Notes alla, show combined notes from v.1 to v.3