Re: [netmod] module-versioning should require any solution to describe labels for drafts

Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de> Mon, 22 June 2020 15:41 UTC

Return-Path: <j.schoenwaelder@jacobs-university.de>
X-Original-To: netmod@ietfa.amsl.com
Delivered-To: netmod@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A46A13A0DD1 for <netmod@ietfa.amsl.com>; Mon, 22 Jun 2020 08:41:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7c8-xttYYh6M for <netmod@ietfa.amsl.com>; Mon, 22 Jun 2020 08:41:32 -0700 (PDT)
Received: from atlas5.jacobs-university.de (atlas5.jacobs-university.de [212.201.44.20]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88D843A0D69 for <netmod@ietf.org>; Mon, 22 Jun 2020 08:41:31 -0700 (PDT)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by atlas5.jacobs-university.de (Postfix) with ESMTP id E5405691; Mon, 22 Jun 2020 17:41:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from atlas5.jacobs-university.de ([10.70.0.198]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10032) with ESMTP id rsVkcNN0-G9J; Mon, 22 Jun 2020 17:41:29 +0200 (CEST)
Received: from hermes.jacobs-university.de (hermes.jacobs-university.de [212.201.44.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "hermes.jacobs-university.de", Issuer "DFN-Verein Global Issuing CA" (verified OK)) by atlas5.jacobs-university.de (Postfix) with ESMTPS; Mon, 22 Jun 2020 17:41:29 +0200 (CEST)
Received: from localhost (demetrius5.irc-it.jacobs-university.de [10.70.0.222]) by hermes.jacobs-university.de (Postfix) with ESMTP id 7688420154; Mon, 22 Jun 2020 17:41:29 +0200 (CEST)
X-Virus-Scanned: amavisd-new at jacobs-university.de
Received: from hermes.jacobs-university.de ([212.201.44.23]) by localhost (demetrius5.jacobs-university.de [10.70.0.222]) (amavisd-new, port 10028) with ESMTP id 5bsk37W_ANtK; Mon, 22 Jun 2020 17:41:29 +0200 (CEST)
Received: from localhost (anna.jacobs.jacobs-university.de [10.50.218.117]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by hermes.jacobs-university.de (Postfix) with ESMTPS id 32CFA200E4; Mon, 22 Jun 2020 17:41:29 +0200 (CEST)
Date: Mon, 22 Jun 2020 17:41:28 +0200
From: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
To: "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com>
Cc: "netmod@ietf.org" <netmod@ietf.org>
Message-ID: <20200622154128.rn5v2u4kci2icdga@anna.jacobs.jacobs-university.de>
Reply-To: Juergen Schoenwaelder <j.schoenwaelder@jacobs-university.de>
Mail-Followup-To: "Sterne, Jason (Nokia - CA/Ottawa)" <jason.sterne@nokia.com>, "netmod@ietf.org" <netmod@ietf.org>
References: <DM5PR08MB2633618B426287D32C6D5D219B970@DM5PR08MB2633.namprd08.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <DM5PR08MB2633618B426287D32C6D5D219B970@DM5PR08MB2633.namprd08.prod.outlook.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/VAHDRzRFc7_rD3pcUeepjXfkAdY>
Subject: Re: [netmod] module-versioning should require any solution to describe labels for drafts
X-BeenThere: netmod@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: NETMOD WG list <netmod.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/netmod>, <mailto:netmod-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/netmod/>
List-Post: <mailto:netmod@ietf.org>
List-Help: <mailto:netmod-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/netmod>, <mailto:netmod-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jun 2020 15:41:35 -0000

I have RFCXXXX 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 authors will get this all done
correctly during module revision (and which problem does all of this
fix)?

/js

On Mon, Jun 22, 2020 at 03:24:33PM +0000, Sterne, Jason (Nokia - CA/Ottawa) wrote:
> 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-netmod-yang-semver.txt
> 
> I think we probably need to require that same information for any revision label scheme. I'd suggest we put something along these lines into the module-versioning draft:
> 
> Any revision label scheme MUST describe how labels are selected for new YANG modules that are under development, and how labels are selected for modules in IETF RFCs that are being updated (e.g. a "bis" version is under development).
> 
> (should we drop the "in IETF RFCs" ? )
> 
> Jason
> 

> _______________________________________________
> netmod mailing list
> netmod@ietf.org
> https://www.ietf.org/mailman/listinfo/netmod


-- 
Juergen Schoenwaelder           Jacobs University Bremen gGmbH
Phone: +49 421 200 3587         Campus Ring 1 | 28759 Bremen | Germany
Fax:   +49 421 200 3103         <https://www.jacobs-university.de/>