RELEASE.md (1092B)
1 # Release Process 2 3 ## Checklist 4 5 - [ ] no manual version bump needed: the version is derived from the git tag 6 by scripts/get_version.sh and feeds both meson.build's project version 7 and doxygen's PROJECT_NUMBER (generated into doc/doxygen/version.doxy). 8 There is no configure.ac. Just make sure the release is tagged (below). 9 - [ ] add entry to ChangeLog 10 - [ ] update debian/changelog (contrib/bump does this, or 11 contrib/ci/debian-package-job.sh via `gbp dch`) 12 - [ ] check CI (contrib/ci, buildbot.taler.net) 13 - [ ] tag with dev tag, test in staging environment 14 - [ ] tag with release tag 15 - [ ] upload to GNU mirrors 16 - [ ] upload Debian packages to deb.taler.net 17 18 ## Versioning 19 20 Releases use `$major.$minor.$patch` semantic versions. The corresponding git 21 tag is `v$major.minor.$patch`. 22 23 Versions that are tested in staging environments typically use 24 `v$major.$minor.$patch-dev.$n` tags. 25 26 Debian package versions used by the CI packaging jobs are derived from the 27 highest SemVer-compatible tag by contrib/ci/debian-version.py (validated by 28 contrib/ci/test_version.py).