Hi Neels,
On Mon, Oct 30, 2017 at 06:39:26PM +0100, Neels Hofmeyr wrote:
Yay, excellent!
thanks!
So we can make those three-monthly release feeds we're planning to start in december by essentially pinning the versions of a 'latest' build. (They won't really be "stable" releases, just pinned ones.)
ACK.
We could theoretically also just copy the 'latest' binaries on a given day to a different download folder without maintaining OBS builds ... but probably better to do actual builds instead for easier "backport" releasing if needed.
we should have "network:osmocom:release-xyz" feeds for each of the releases we create.
We'll probably do a release tagging round in all repositories for each such cycle, 4 times a year, and are free to do more release tags in-between to make 'latest' benefit from fixes or features.
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?