RELEASE.md (1406B)
1 # Release Process 2 3 ## Checklist 4 5 - [ ] bump version in meson.build (`project(... version:)`; the tag is what 6 `scripts/get_version.sh` reports) 7 - [ ] if `ANASTASIS_PROTOCOL_CURRENT` (src/restclient/anastasis_api_config.c) 8 or the version served by `/config` 9 (src/backend/anastasis-httpd_config.c) changed, say so in NEWS, state 10 whether stored data is still readable, and confirm which 11 taler-typescript-core release speaks the same protocol version -- 12 the C and TypeScript clients have to bump in lock-step 13 - [ ] if a public library's ABI changed, bump its entry in `libltversions` 14 in meson.build, and say so in NEWS (out-of-tree users such as 15 anastasis-gtk need to know) 16 - [ ] if `src/stasis/stasis-*.sql` gained a migration, confirm it was tested 17 against a database created by the *previous* release, not only against 18 a fresh one 19 - [ ] add entry to NEWS 20 - [ ] add entry to ChangeLog 21 - [ ] add entry to debian/changelog 22 - [ ] check CI (contrib/ci, buildbot.taler.net) 23 - [ ] tag with dev tag, test in staging environment 24 - [ ] tag with release tag 25 - [ ] upload to GNU mirrors 26 - [ ] upload Debian packages to deb.taler.net 27 28 ## Versioning 29 30 Releases use `$major.$minor.$patch` semantic versions. The corresponding git 31 tag is `v$major.minor.$patch`. 32 33 Versions that are tested in staging environments typically use 34 `v$major.$minor.$patch-dev.$n` tags. 35