YANG Versioning Weekly Call Minutes - 2022-05-17 We further discussed the use of per-element NBC/BC marking: - mixing a lot of detailed per-element history in a module may not be as clean as keeping it as "the current API" - in some more extreme cases, could end up with a module that is more history than API - doesn't handle an element that is removed from a module - less likely to get it correct from authors - if a tool can do it anyway, then why mark it all up right in the module ? - versioning in other areas is often "aggregated" at some level - TBD if it would have some complications/issues when considering branching and porting elements from one branch to another
Proposal a: - NBC & BC per-element tags, mandatory when the diff tool is going to guess wrong (e.g. a description change is actually an NBC change instead of the default assumption of being editorial) - may be added to any element at author's discretion (i.e. can mark things the diff tool will also identify) Proposal b: - NBC marker only - always mandatory Proposal c: - Proposal A, but IETF MUST always mark NBC against elements We also briefly discussed other metadata (e.g. "introduced in" tag) but we were leaning away from these towards the end of the meeting. Jason ---------------------------------------------- Versioning work on Github: https://github.com/netmod-wg/yang-ver-dt ---------------------------------------------- Weekly webex call details: Meeting number (access code): 161 096 5630 Meeting password: semver? Occurs every Tuesday effective Tuesday, November 16, 2021 from 9:00 AM to 10:00 AM, (UTC-05:00) Eastern Time (US & Canada) 9:00 AM | (UTC-05:00) Eastern Time (US & Canada) | 1 hr https://ietf.webex.com/ietf/j.php?MTID=me2c6491ebcc37b8127c1244d244d2754 Tap to join from a mobile device (attendees only) +1-650-479-3208,,1610965630## Call-in toll number (US/Canada)
_______________________________________________ netmod mailing list netmod@ietf.org https://www.ietf.org/mailman/listinfo/netmod
