summaryrefslogtreecommitdiff
path: root/maint
diff options
context:
space:
mode:
authorSimon McVittie <smcv@collabora.com>2022-07-23 11:21:39 +0100
committerSimon McVittie <smcv@collabora.com>2022-07-23 11:23:06 +0100
commit8e0290fcc8908c89788c3fe254708c4b3cc02186 (patch)
tree711b087993ebea0d77c966dd5f413d98579feac7 /maint
parent3758e5b1648a26fd2343db3c804d32a29ae75ff8 (diff)
downloaddbus-8e0290fcc8908c89788c3fe254708c4b3cc02186.tar.gz
release-checklist: Add a reminder to update both Autotools and Meson
Signed-off-by: Simon McVittie <smcv@collabora.com>
Diffstat (limited to 'maint')
-rw-r--r--maint/release-checklist.md9
1 files changed, 8 insertions, 1 deletions
diff --git a/maint/release-checklist.md b/maint/release-checklist.md
index 5de87933..07e1067f 100644
--- a/maint/release-checklist.md
+++ b/maint/release-checklist.md
@@ -6,6 +6,9 @@ To make a release of D-Bus, do the following:
- verify that the libtool versioning/library soname is
changed if it needs to be, or not changed if not
+ - remember to update **both** `configure.ac` **and** `meson.build`
+ - CMake takes the version number from `configure.ac` and so should not
+ need updating
- update the file NEWS based on the git history
@@ -18,6 +21,9 @@ To make a release of D-Bus, do the following:
- the version number should have major.minor.micro, even
if micro is 0, i.e. "1.0.0" and "1.2.0" not "1.0"/"1.2"; the micro
version should be even for releases, and odd for intermediate snapshots
+ - remember to update **both** `configure.ac` **and** `meson.build`
+ - CMake takes the version number from `configure.ac` and so should not
+ need updating
- "make distcheck" (DO NOT just "make dist" - pass the check!)
@@ -31,7 +37,8 @@ To make a release of D-Bus, do the following:
then simply created an unsigned annotated tag:
"git tag -a -m 'Released X.Y.Z' dbus-X.Y.Z".
- - bump the version number up in configure.ac (so the micro version is odd),
+ - bump the version number up in `configure.ac` and `meson.build`
+ again (so the micro version is odd),
and commit it. Make sure you do this *after* tagging the previous
release! The idea is that git has a newer version number
than anything released. Similarly, bump the version number of