New "osmocom:latest" package feed

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.de
Fri Nov 3 17:34:11 UTC 2017


On Mon, Oct 30, 2017 at 09:28:06PM +0100, Harald Welte wrote:
> I'm wondering if it wouldn't make more sense to have git branches (as opposed to tags)
> for those "overall project releases".  This way we could actually - if needed - add
> fixes or other backports to the respective release branch in the repository, and 
> the OBS builds for that release would simply follow those branches?

Until we backport something, a tag would suffice, but indeed, using branches
could simplify (skip the need for) updating the git target for
"network:osmocom:release-xyz" feeds.

~N

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.osmocom.org/pipermail/openbsc/attachments/20171103/6a07c5ca/attachment.bin>


More information about the OpenBSC mailing list