You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
./standard/ietf/DRAFT hasn't been updated for 7 years and contains at least one module that can conflict with ./experimental/ietf-extracted-YANG-modules.
The latter file is @2015-10-09, which means that it's necessary to search ./experimental before ./standard/ietf, whereas I think it might be better to search ./standard/ietf first.
Anyway I suggest that ./standard/ietf/DRAFT be emptied or deleted. Possibly it would make sense for some or all of ./experimental/ietf-extracted-YANG-modules to live there?
The text was updated successfully, but these errors were encountered:
Follow-up on this. I checked (and maybe I'm looking in the wrong place), but the last check of this https://github.com/YangModels/yang/commits/main/experimental/ietf-extracted-YANG-modules was at the end of 2023. When I look in the main branch of the repo, there is nothing in the ietf-extracted-YANG-modules from 2024. Are they on a different branch, or are the automated tools broken?
As far as I can see the team that was extracting the experimental modules, etc., from the IETF drafts and committing them to YangModels/yang have stopped doing this. They are only running scripts to populate yangcatalog.org as far as I can see. The automated tools may be broken, but the team that did that has not approached me at all.
./standard/ietf/DRAFT
hasn't been updated for 7 years and contains at least one module that can conflict with./experimental/ietf-extracted-YANG-modules
.The latter file is
@2015-10-09
, which means that it's necessary to search./experimental
before./standard/ietf
, whereas I think it might be better to search./standard/ietf
first.Anyway I suggest that
./standard/ietf/DRAFT
be emptied or deleted. Possibly it would make sense for some or all of./experimental/ietf-extracted-YANG-modules
to live there?The text was updated successfully, but these errors were encountered: