search

netmod-wg / yang-ver-dt

Repo for use by the YANG versioning design team
3 stars 3 forks source link

Specify compatibility constraints as meta-data #76

Open Reshad-Rahman opened 3 years ago

Reshad-Rahman commented 3 years ago

Notes from virtual interim on Dec 14th 2020:

Thanks everyone for the feedback and comments on the mailing list and during the interim.

For the issue of revision-or-derived-compatible, there seems to be consensus that “revision-or-derived” is useful but compatibility constraints on imported modules is better defined outside of the modules. So we will close https://github.com/netmod-wg/yang-ver-dt/issues/75, and open a new issue to look at how to define these constraints as meta-data elsewhere (e.g. in packages)

Reshad-Rahman commented 3 years ago

See email from Juergen: https://mailarchive.ietf.org/arch/msg/netmod/KZtb98sZygJeKaCVWCSxd1HunuY/

rgwilton commented 3 years ago

Discussed, but will leave open to come back to. Reshad to think about this some more.

Reshad-Rahman commented 2 years ago

I might be drawing a blank here, but looking back at the issue and emails, I think we don't have anything extra to add in packages. YANG packages already have lists of packages/modules and the desired revision-label/date. As long as a package include the right "versions", the package will not be "broken". I think this is good enough? Or do we need to add text in the document for this?

Reshad-Rahman commented 2 years ago

Dec 14th meeting: do we need to support version range in YANG packages or is 1 version good enough?