aboutsummaryrefslogtreecommitdiffstats
path: root/TODO-RELEASE
diff options
context:
space:
mode:
authorPau Espin Pedrol <pespin@sysmocom.de>2018-05-03 15:01:47 +0200
committerPau Espin Pedrol <pespin@sysmocom.de>2018-05-03 15:21:24 +0200
commit01dd570de80ef6838c77e03677444916abdc5863 (patch)
treeb63fb2d1c969e6e30871c67fd9134a309ca8e46a /TODO-RELEASE
parent0b0f9088591fafe332c3e85fc9563960c66a2910 (diff)
osmo-release.sh: Always generate entire commit changelog
Before this commit, for library projects (containing LIBVERSION in some Makefile), the entire commit list was not stored into the changelog, but only a few lines from TODO-RELEASE files. This is a bad approach for several reasons. First, because that file was only aimed at containing API/ABI breaks, and not the full relevant changeset (like bugfixes, new features, etc.). Second, because it relies on every developer making API/ABI changes to remember to store the change in there during commit break time. Let's instead always store the entire commit list in changelog, and let's use TODO-RELEASE only as a list of hints for the maintainer to help him evaluate how LIBVERSION needs to be bumped for each library. Other tools such as osmo-abi-check.git can be used to help with the process of decission too. Let's take the opportunity too to only commit stuff already added to the staging area, as it proved easier to manage from my personal experinece making latest releases. Change-Id: Ibf662173ce2b4ff3966e9ad5f56c65dfb13607ff
Diffstat (limited to 'TODO-RELEASE')
-rw-r--r--TODO-RELEASE4
1 files changed, 2 insertions, 2 deletions
diff --git a/TODO-RELEASE b/TODO-RELEASE
index 16496d68..146ab333 100644
--- a/TODO-RELEASE
+++ b/TODO-RELEASE
@@ -1,6 +1,6 @@
# When cleaning up this file: bump API version in corresponding Makefile.am and rename corresponding debian/lib*.install
-# according to https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html#Updating-version-info
-# In short:
+# according to https://osmocom.org/projects/cellular-infrastructure/wiki/Make_a_new_release
+# In short: https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html#Updating-version-info
# LIBVERSION=c:r:a
# If the library source code has changed at all since the last update, then increment revision: c:r + 1:a.
# If any interfaces have been added, removed, or changed since the last update: c + 1:0:0.