CheckList

• Create an issue with this checklist in the release milestone.
• If major release (YYYY.XX.00), create a branch (YYYY.XX.xx) (xx is really xx, example: 2018.01.xx)
• If major release,Change QA Jenkins job to build the new branch, enable the job continuous deploy
• create on ReadTheDocs project the version build for YYYY.XX.xx (click on "Versions" and activate the version of the branch)
• Test on QA http://qa.mapstore2.geo-solutions.it/mapstore/
  • Any fix must be done on YYYY.XX.mm. The fixes will be manually merged on master
  • Test everything, not only the new features
• Test Binary
• Update CHANGELOG.md. Instructions
• Commit the changelog to the release branch
• Create a github draft release pointing to the branch YYYY.XX.mm.

  The Release name should follow be named YYYY.XX.mm where YYYY is the year, XX is the incremental number of the release for the current year (starting from 01) and the second number mm is an incremental value (starting from 00) to increment for minor releases. Insert the tag vYYYY.XX.mm (notice the initial 'v' for the tag) to create when the release is published. In the release description describe the major changes and link the Changelog paragraph.

• Launch MapStore2-Releaser Jenkins job setting up the correct name of the version and the branch to build (and wait the end). Note: Using the MapStore2 Releaser allows to write the correct version number into the binary packages.
• Get the latest mapstore.war from the Releaser Jenkins build and upload it to github
• Get the latest mapstore2-YYYY.XX.mm-bin.zip from the Releaser Jenkins build and upload it to github

  from the job configuration page there is a link to access the job workspace to easily download the built WAR and binary package

• Publish the release
• create on ReadTheDocs project the version build for vYYYY.XX.mm (click on "Versions" and activate the version of the tag, created when release was published)
• Port needed commits to master branch (Changelog changes, docs changes...)
• Create a blog post
• Write to the mailing list about the current release news and the next release major changes
• Update the release procedure if needed.
• Close this issue
• Close the related milestone

Info about this release

• Release procedure have to updated with new read the docs setups (copy checks from this issue to the release.md file