Release process (rel 2.0.0 onwards)

🐛 Fix a bug or create a new feature

(it is assumed that you've already cloned the cgimap repo)

• Create a new branch

git checkout -b patch/issue_1234

• Fix the bug, add some new feature, etc.

• Build and run unit tests

Follow the README file for details on how to compile and run tests: https://github.com/zerebubuth/openstreetmap-cgimap

• Commit changes

  • provide a short summary of the issue in the commit message
  • if needed, also add a long text

• Upload branch

git push origin patch/issue_1234

• Create a Pull request on GitHub, discuss changes

A repository owner or collaborator can then merge the pull request into the master branch, assuming unit tests pass.

🚀 Preparing a new release

(Steps for repo owners or collaborators)

• Check out master branch

• git pull

• Edit CMakeLists.txt, change version number in project section.

project(openstreetmap-cgimap`
        `LANGUAGES CXX`
        `VERSION "0.10.0.${CURRENT_TIMESTAMP}"

• Update debian/changelog

  • Add list of changes in this release
  • Stick to the format used by a previous release

• Create new commit "Bump version to 0.x.x" (see git log)

• Tag the new version: git tag v2.0.0

• Upload tag to GitHub: git push --atomic origin master v2.0.0

• Wait for package build to complete successfully. This could take around 10 minutes.

• Based on the new tag, update the draft release with up to date release notes.

https://github.com/zerebubuth/openstreetmap-cgimap/releases

• Check Debian package attachments

• Publish draft version as new release

• Create a new operations ticket on https://github.com/openstreetmap/operations/issues with a link to the most recent release.