git tagging

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
Tue Dec 13 17:29:04 UTC 2016


Hi.

With the migration to gerrit the situation around version tagging become 
even funnier than before. For example right now in libosmocore v0.9.3 
does not exist as a git tag, only as entry in debian/changelog. Versions 
0.9.5 and 0.9.6 are committed in reversed order - see output of
git log --tags --show-notes --decorate | grep 'tag:' | head

So the questions are:
- how can I add tag '0.9.3' to commit 
abc46af90fde9e9435dee5f4f472aec3f68d3353 in libosmocore
- how can we prevent the inverted commit situation as with 0.9.6 and 
0.9.5 in future?
- what's the general guidelines for tagging new versions? Do we go 
through gerrit or ask responsible person (who?) to do it manually? Or 
even auto-tag commit matching certain criteria?

-- 
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