en if we published the RFC at that point it would be 1.1.0
>
> Jason
>
>
> > -Original Message-
> > From: Juergen Schoenwaelder
> > Sent: Monday, June 22, 2020 12:30 PM
> > To: Sterne, Jason (Nokia - CA/Ottawa)
> > Cc: netmod@ietf.org
> > Subj
(Nokia - CA/Ottawa)
> Cc: netmod@ietf.org
> Subject: Re: [netmod] module-versioning should require any solution to
> describe
> labels for drafts
>
> On Mon, Jun 22, 2020 at 04:01:59PM +, Sterne, Jason (Nokia - CA/Ottawa)
> wrote:
> > Hi Juergen,
> >
> >
On Mon, Jun 22, 2020 at 04:01:59PM +, Sterne, Jason (Nokia - CA/Ottawa)
wrote:
> Hi Juergen,
>
> Section 5 in the link below attempts to explain how to manage this (but
> always happy for review of that text to help improve it).
>
> The key is to always ensure there is a unique version for
; From: Juergen Schoenwaelder
> Sent: Monday, June 22, 2020 11:41 AM
> To: Sterne, Jason (Nokia - CA/Ottawa)
> Cc: netmod@ietf.org
> Subject: Re: [netmod] module-versioning should require any solution to
> describe
> labels for drafts
>
> I have RFC at version 1.0.0. I
> On Jun 22, 2020, at 11:41, Juergen Schoenwaelder
> wrote:
>
> I have RFC at version 1.0.0. I make some backwards compatible
> changes. I then make a backwards incompatible change. Then I add more
> backwards compatible changes. Then I remove the backwards incompatible
> change. What are
I have RFC at version 1.0.0. I make some backwards compatible
changes. I then make a backwards incompatible change. Then I add more
backwards compatible changes. Then I remove the backwards incompatible
change. What are the resulting version numbers?
Rhetoric question: How many IETF module aut
Hi guys,
In the latest working copy of the YANG Semver draft we added some text in
section 5 about how to select revision labels for modules that are under
development, or for RFCs that are churning (i.e. bis versions).
https://github.com/netmod-wg/yang-ver-dt/blob/master/yang-semver/draft-ietf
