Hi.

Just a heads-up on recent changes related to Osmocom releases.

In short: read about it at https://osmocom.org/projects/cellular-infrastructure/wiki/Make_a_new_release

Somewhat longer explanation:

In attempt to simplify and structure release process (see https://projects.osmocom.org/issues/1861 ) I've added helper script (osmo-release.mk, installed by recent libosmocore-dev) which attempts to automate as much as possible:

* treat library and non-library projects differently

* autogenerate debian/changelog

* automatically bump version

* cleanup TODO-RELEASE

* checks for missing *_LIBVERSION update

* automatically commit, sign and tag the result

Of course it might fail to do the right thing for multitude of reasons (incorrectly filled TODO-RELEASE, missing tags, missing git-version-gen helper, weird versions in debian/changelog etc) so nothing is pushed automatically. You're expected to inspect the release commit and push it manually (don't forget to push the tag too!).

In general, it works: made libosmo-abis 0.4.0 and osmo-bts 0.6.0 releases using it. The patches to make it available to other *osmo* projects are under review.

Now, if you've read that far, you must be really interested in making release for some Osmocom project (or just really bored :) Either way, please do any of the following:

* read the wiki page linked above and see if anything unclear/poorly written/needs corrections

* suggest further updates to release policy described in there

* review corresponding patches in gerrit

* suggest further automation step (ideally, as a patch to osmo-release.mk ;)

* try "make release" for one of the projects not mentioned above (if you have sufficient rights to push tags to gerrit)

* have a look at recent libosmo-abis (>=0.4.0) and osmo-bts (>=0.6.0) and see if anything is broken

N. B: release helper expects version to follow http://semver.org/ - this has been raised in ML and no objections followed. Please adhere to it for all future versions.