16 Dec
2016
16 Dec
'16
3:58 p.m.
Sounds good, but how do we keep track which libosmocore version a dependent
project requires? When I add foo to libosmocore and use foo in openbsc, I will
definitely forget which needs which by the time a release is made...
Write down required bumps in TODO-RELEASE of libosmocore?
~N
On Fri, Dec 16, 2016 at 02:18:35PM +0100, Max wrote:
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.
--
Max Suraev <msuraev(a)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
* Geschaeftsfuehrer / Managing Director: Harald Welte
--
- Neels Hofmeyr <nhofmeyr(a)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