16 Dec
2016
16 Dec
'16
4:04 p.m.
I'd say write in both:
- TODO-RELEASE in OpenBSC/OsmoBTS/whatever: "bump libosmo-X with change
Y before release"
- TODO-RELEASE in libosmo-*: "change Y: blah-blah"
Unless someone can come with easier or more automatable scheme.
On 16.12.2016 16:58, Neels Hofmeyr wrote:
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
--
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