How to Release

Note: This follows the procedure used for GeoStore. You can try to improve this procedure by using the improvement commands on GeoStore wiki.

Notes:

Wherever you see geosolutions-2.M.x it means to replace M with the number of the major release. (e.g geosolutions-2.0.x, geosolutions-2.1.x.)
Wherever you see geosolutions-2.M.0 it means to replace M with the number of the major release. (e.g geosolutions-2.0.0, geosolutions-2.1.0.)
Wherever you see geosolutions-2.M.m it means to replace M with the number of the major release. And m with the minor (geosolutions-2.0.x, geosolutions-2.1.x.)

Major Release

create a new branch from master called geosolutions-2.M.x The number should be the same of the current version on master.
On the branch geosolutions-2.M.x.
- Fix the version pom.xml (see this) to geosolutions-2.M.0. (e.g geosolutions-2.1.0)
- Run mvn deploy (or better indicated on readme.md) to deploy artifacts on maven.geo-solutions.it .
- Create a new GitHub release here to tag the commit just committed:
  - select the branch geosolutions-2.M.x
  - the tag geosolutions-2.M.0. (the tag will be applied on release publishing)
  - as title geosolutions-2.M.0
  - add a small description about the release
  - Click on publish. This will create the tag on the current head of the branch selected (where the version has been just fixed)
- Change the version change to (geosolutions-2.M-SNAPSHOT) Commit this change on geosolutions-2.M.x branch.
On master: Increase the major version on master to geosolutions-2.(M+1)-SNAPSHOT. (e.g geosolutions-2.2-SNAPSHOT`) Commit this change on master.

basically :