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/gerrit-log@lists.osmocom.org/.
pespin gerrit-no-reply at lists.osmocom.orgpespin has posted comments on this change. ( https://gerrit.osmocom.org/c/libosmocore/+/23240 ) Change subject: TODO-RELEASE: Request increasing _LAST_OSMOVTY_NODE next release ...................................................................... Patch Set 1: I think we already discussed this and agreed that this kind of issues are expected with master, that is, one must ensure to always run latest master of everything if not running tagged releases. In any case, one can precisely look at TODO-RELEASE of related components to find the possible ABI breakages or any kind of changes (already done!) which may provoke those. I think it makes sense to do that instead of pretending to delay several or tons of tasks until release time and then be drown under them when trying to apply all of them at the same time, potentially breaking stuff and having to re-release, etc. So the earlier breakage happens in master imho is best, because everyone has more time to adapt to it and fix stuff in master itself. -- To view, visit https://gerrit.osmocom.org/c/libosmocore/+/23240 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: libosmocore Gerrit-Branch: master Gerrit-Change-Id: Idfe1e7d97f3f29fc219e80dcb6ce6bb768733adf Gerrit-Change-Number: 23240 Gerrit-PatchSet: 1 Gerrit-Owner: laforge <laforge at osmocom.org> Gerrit-Reviewer: Jenkins Builder Gerrit-CC: pespin <pespin at sysmocom.de> Gerrit-Comment-Date: Fri, 05 Mar 2021 13:43:29 +0000 Gerrit-HasComments: No Gerrit-Has-Labels: No Gerrit-MessageType: comment -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20210305/cd1146ed/attachment.htm>