Change in libosmocore[master]: TODO-RELEASE: Request increasing _LAST_OSMOVTY_NODE next release

laforge gerrit-no-reply at
Fri Mar 5 12:48:31 UTC 2021

laforge has posted comments on this change. ( )

Change subject: TODO-RELEASE: Request increasing _LAST_OSMOVTY_NODE next release

Patch Set 1:

> Patch Set 1:
> I only see the comment in TODO-RELEASE? I would have expected also the change itself.
> It's enough work to do the release itself, so let's no delay extra jobs until that time. The TODO-RELEASE file is useful to know which stuff already done triggers some required change during release time.

The point is: This should always be done just ahead of a release, every time we increment the SO version, there should be some new reserved logging groups in the header file.  While we then maintain the SO version, we replace reserved groups with newly-introduced groups without breaking ABI.

I can do it now but that would mean an ABI breakage right now, just after we tagged the release, and it will likely be broken again and again during further development.

I've added the comment so we don't forget doing this when actually incrementing SOversion.

To view, visit
To unsubscribe, or for help writing mail filters, visit

Gerrit-Project: libosmocore
Gerrit-Branch: master
Gerrit-Change-Id: Idfe1e7d97f3f29fc219e80dcb6ce6bb768733adf
Gerrit-Change-Number: 23240
Gerrit-PatchSet: 1
Gerrit-Owner: laforge <laforge at>
Gerrit-Reviewer: Jenkins Builder
Gerrit-CC: pespin <pespin at>
Gerrit-Comment-Date: Fri, 05 Mar 2021 12:48:31 +0000
Gerrit-HasComments: No
Gerrit-Has-Labels: No
Gerrit-MessageType: comment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the gerrit-log mailing list