[gnome-desktop/mcatanzaro/libversion] Improve library versioning comment
- From: Michael Catanzaro <mcatanzaro src gnome org>
- To: commits-list gnome org
- Cc:
- Subject: [gnome-desktop/mcatanzaro/libversion] Improve library versioning comment
- Date: Mon, 21 Mar 2022 19:47:58 +0000 (UTC)
commit 079041b9b39bcd0591e6bf7c29e32b0900cefbfb
Author: Michael Catanzaro <mcatanzaro redhat com>
Date: Mon Mar 21 14:41:56 2022 -0500
Improve library versioning comment
Mention compat_libversion.
In practice, we don't update libversion if source code has not changed.
Mention this.
We should bump the version more aggressively after branching, to avoid
identical versions on different branches.
meson.build | 8 +++++++-
1 file changed, 7 insertions(+), 1 deletion(-)
---
diff --git a/meson.build b/meson.build
index 1f3997dc..c8e82a7b 100644
--- a/meson.build
+++ b/meson.build
@@ -7,12 +7,18 @@ project('gnome-desktop', 'c',
],
)
-# Before making a release, the libversion string should be modified.
+# Before making a release that changes the source code, the libversion and
+# compat_libversion strings should be modified. (No need to touch these releases
+# with no code changes.)
#
# * Bump the first component if binary compatibility has been broken; or
# * Bump the second component if new APIs are added; or
# * Bump the third component otherwise.
#
+# After creating a new stable branch, the next release on the main branch should
+# bump the second component to ensure we don't wind up with the same libversion
+# for different releases on different branches.
+#
# When bumping the first component version, set the second and third components
# to 0. When bumping the second version, set the third one to zero.
#
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]