> On Mar 15, 2026, at 19:11, Michael Richardson <[email protected]> wrote: > > 5. " A release tagging mechanism should be defined to track the > intermediate versions referenced by WG I-Ds and by the RFC, once > published. This can come in the form of a 'git tag' or by having a > branch that corresponds to the version of the draft."
My primary concern with new process aligns here. The underlying question is how "IETF" publishes that they've "shipped" a new version from the repostories? There's a headache just declaring when you might do a cut to align with an updated I-D. Or, similarly, publication as an RFC. For things that no longer has an I-D to bind to? There's also the matter of how the various elements across our module sets get their "consistent cut". There's no trivial answer here. It eventually devolves into IETF needing to have someone be a release manager for the repos. Not that we necessarily pay attention to many of these things today.... -- Jeff _______________________________________________ OPSAWG mailing list -- [email protected] To unsubscribe send an email to [email protected]
