Using repo to make 'regular' releases

This is merely a historical archive of years 2008-2021, before the migration to mailman3.

A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.

Max msuraev at sysmocom.de
Wed Apr 26 08:13:37 UTC 2017


I think it's really bad idea to have different versions pointing to the same commit:
* it's extra headache for testing - we either have to figure out "duplicate" versions
to avoid useless work or do meaningless testing
* if while making point fix we forget about this duplicity we might end-up with
17.04.1 and 17.06.1 diverged while 17.04 and 17.06 were the same thing for particular
component
* it makes it impossible to mark any component-specific changes between global releases

On 26.04.2017 10:07, Pau Espin Pedrol wrote:
>
>>> It seems to me we could completely replace individual project versions
>>> with the overall release ("17.6.0"), *if* we accept that non-changing
>>> projects would have several versions tagging exactly the same code
>>> state.
>>
>> So far I really don't like that idea.  It just feels wrong, somehow.  I
>> cannot really explain it.
>
> I have to say I'm not particularly against this idea from Neels. It would simplify
> a lot naming of the versions of all projects.
>
>


-- 
Max Suraev <msuraev 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 
* Geschaeftsfuehrer / Managing Director: Harald Welte 







More information about the OpenBSC mailing list