Hi Per,
Perhaps this formulation is still to arbitrary that both revision-date and
ys:version can be used? The formulation is taken from the module
versioning document almost verbatim, but there have been a few
iterations of this paragraph.
Yes we went through a few iterations of that text. At some point we even had
text about 1 copy of each module and use of soft links etc...But my
recollection is that at the end of our weekly discussions, and maybe that was
never reflected in the document, is that we wanted to allow use of both
revision-date and ys:version in filenames.
Regards,Reshad.
On Monday, July 8, 2024 at 06:45:32 AM EDT, Per Andersson
<[email protected]> wrote:
Hi Reshad,
On Sun, Jul 7, 2024 at 3:59 PM Reshad Rahman <[email protected]> wrote:
>
> Hi Per,
>
> Thanks for doing the work. I just took a quick look at the document and I
> have 1 basic comment/question:
Thanks for the review!
> Section 2 has the following text where it says "instead of". IIRC when we had
> this in the module versioning document, the intention was to allow both forms.
>
> If a revision has an associated YANG semantic version (ys:version)
> then it is RECOMMENDED that the YANG semantic version is used instead
> of the revision date in the file name of a YANG file, where it takes
> the form:
>
> module-or-submodule-name [['@' revision-date]['#' ys:version]]
> ( '.yang' / '.yin' )
>
> E.g., [email protected] or
> acme-router-module#2.0.3.yang.
I have uploaded a new revision which says
If a revision has an associated YANG semantic version (ys:version)
then it MAY use the YANG semantic version instead of the revision date
in the file name of a YANG file, where it takes the form:
Perhaps this formulation is still to arbitrary that both revision-date and
ys:version can be used? The formulation is taken from the module
versioning document almost verbatim, but there have been a few
iterations of this paragraph.
--
Pell
_______________________________________________
netmod mailing list -- [email protected]
To unsubscribe send an email to [email protected]
