libosmocore changes / release process

[Neels Hofmeyr]

When I now change pretty much anything in libosmocore that I want to use in
e.g. openbsc.git, I would like to bump the minor revision and reference that in
other projects' configure.ac.

The effort is ok if it entails only tagging a revision and using that elsewhere.
However, this has come down to a lengthy process: 

"
    cleanup TODO-RELEASE file if not empty, bumping API versions accordingly (see comments in TODO-RELEASE)
    update debian/changelog using "gbp dch" command
"
https://osmocom.org/projects/cellular-infrastructure/wiki/Make_a_new_release#Make-a-Release

So, pretty much every commit in libosmocore will be followed by another commit
that is adjusting the changelog...? :/

Should we adjust the changelog along with pretty much any change used outside
of libosmocore? :/  (probably not, because reverting anything is made cumbersome)

Should we rather, like, make a libosmocore release only once a week and somehow
track wich other projects need a bump to the required libosmocore version?

I think most projects out there make a release tag only every now and then. We
could limit to noting the required libosmocore change-id in other projects'
commit logs until the next (minor) release is made...?

Can we add a fourth level of version that doesn't require a changelog/debian
release? So for every small change I make I would tag 0.9.6.1, 0.9.6.2, etc.,
and at some point we make 0.9.7 along with a changelog adjustment?

Thoughts?

~N

-- 
- Neels Hofmeyr <nhofmeyr at sysmocom.de>          http://www.sysmocom.de/
=======================================================================
* sysmocom - systems for mobile communications GmbH
* Alt-Moabit 93
* 10559 Berlin, Germany
* Sitz / Registered office: Berlin, HRB 134158 B
* Geschäftsführer / Managing Directors: Harald Welte
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20161216/8587d3ee/attachment.bin>