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/.
Neels Hofmeyr nhofmeyr at sysmocom.deOn Sun, Apr 23, 2017 at 01:04:56PM +0200, Holger Freyther wrote: > Hi, > > for the topic of making "releases" I wondered if we want to explore using "repo" to tie the different Osmocom repositories into a single "release". Below is an example "default.xml" that would make up a release. The default.xml would be maintained in a git repository that we could tag, e.g. something like v201704.1 (vYYYYMM.MINOR). > > I could envision we have: > > * A simple build shell script to build/install everything > * A script to update (and tag) the default.xml to make new releases available. I like the central handle on dependencies, but I don't really like XML. Why not use the git submodules approach? Can't submodules tag specific revisions? ~N -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 819 bytes Desc: Digital signature URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20170423/9a0b8e9b/attachment.bin>