Re: libosmocore changes / release process

Hi.

I think making new release from libosmocore master just because something in OpenBSC (or other reverse dependency) master requires new functionality is just a waste of efforts. Instead I suggest to make it simple:

- recent master version always requires recent master version of all the libraries (libosmo*): it might still work with some earlier version but that just means you're lucky

- release version shall require appropriate release version of library

This way we only have to make release for libosmo* when we're about to make release of OpenBSC, OsmoBTS etc. which does not happen that often.