libosmocore[master]: gb: optionally allow nsip packets only from a specific host

Neels Hofmeyr gerrit-no-reply at lists.osmocom.org
Thu Oct 19 17:06:46 UTC 2017


Patch Set 2:

> Actually, I think we should start to avoid TODO-RELEASE and tag a
 > new release with updated LIBVERSION every time we break ABI or API
 > compatibility.

Let's discuss / clarify this when we next get the chance to talk; when ABI or API compat is being broken, an immediate release should happen, when we just add new things in a non-breaking way, a TODO_RELEASE entry should suffice. right?

In detail, how would dexter go about this? IIUC this commit still needs to be as it is, with a TODO_RELEASE entry, and *only when this got accepted and merged* is it possible to run a 'make release', sign the tag and bump the versions, apply changelog, push the git version tag, apply depending callers' required-revision bumps. right?

I guess we need a release manager hat, and every time a change to a TODO_RELEASE has been merged, there needs to be some bump to the release manager to fire a new release. Alternatively, the release manager hat makes sure that the individual developers follow up with a release after the ABI/API changes have been merged.

-- 
To view, visit https://gerrit.osmocom.org/4317
To unsubscribe, visit https://gerrit.osmocom.org/settings

Gerrit-MessageType: comment
Gerrit-Change-Id: Ifeb201d9006eec275a46708007ff342cdfc14e45
Gerrit-PatchSet: 2
Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Owner: dexter <pmaier at sysmocom.de>
Gerrit-Reviewer: Harald Welte <laforge at gnumonks.org>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: Neels Hofmeyr <nhofmeyr at sysmocom.de>
Gerrit-HasComments: No


More information about the gerrit-log mailing list