Seedstack Release Guide

Versioning and Release overview

Seedstack version is declared in pom.xml file of distribution module. This project is used as a bom.

Releasing a new version starts with updating the version in this project:

mvn versions:set versions:commit -DnewVersion=19.11-SNAPSHOT

Version numbers are formated as follows: Version number = year.month<.revision> Where month can be:

• 1 (January)
• 4 (April)
• 7 (July)
• 11 (November)

Release build process itself is triggered by a commit where "-SNAPSHOT" has been removed from version number.

Note: the tag associated with version x.y.z includes pom.xml files with x.y.z-SNAPSHOT versions. (The tag is not on a x.y.z version.)

Release Process

The first step is to identify components to be released, so as to update their version in distribution's pom.xml.

Each component is then released invidually, ending with distribution project

This list can be established based on:

1. bintray
2. github

For each component:

• Read CHANGELOG.md file to see if a new release is required, and if changes required an update of distribution.
• Read pom.xml to see if component depends on -SNAPSHOT dependencies. If yes, dependency must be released first.

Note some projects are updated outside of release process:

• samples
• website
• seedstack.github.io