commit 01dd570de80ef6838c77e03677444916abdc5863
author Pau Espin Pedrol <pespin@sysmocom.de> Thu May 03 15:01:47 2018 +0200
committer Pau Espin Pedrol <pespin@sysmocom.de> Thu May 03 15:21:24 2018 +0200
tree b63fb2d1c969e6e30871c67fd9134a309ca8e46a
parent 0b0f9088591fafe332c3e85fc9563960c66a2910

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