Re: [netmod] Fwd: New Version Notification for draft-verdt-netmod-yang-versioning-reqs-01.txt

Martin Bjorklund <mbj@tail-f.com> Fri, 09 November 2018 13:42 UTC

Return-Path: <mbj@tail-f.com>
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 34186130E04; Fri, 9 Nov 2018 05:42:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-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 7yMTMNN7P8gi; Fri, 9 Nov 2018 05:42:04 -0800 (PST)
Received: from mail.tail-f.com (mail.tail-f.com [46.21.102.45]) by ietfa.amsl.com (Postfix) with ESMTP id 5B405130DFB; Fri, 9 Nov 2018 05:42:04 -0800 (PST)
Received: from localhost (h-40-120.A165.priv.bahnhof.se [94.254.40.120]) by mail.tail-f.com (Postfix) with ESMTPSA id 9AA7C1AE0493; Fri, 9 Nov 2018 14:42:03 +0100 (CET)
Date: Fri, 09 Nov 2018 14:42:03 +0100 (CET)
Message-Id: <20181109.144203.1456851344567787622.mbj@tail-f.com>
To: jclarke@cisco.com
Cc: netmod@ietf.org, netmod-ver-dt@ietf.org
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <a1bd7f74-19d6-c8bc-a34d-79ac0ac866e0@cisco.com>
References: <37f05b48-5fe7-82b4-ae32-9b856596e6a2@cisco.com> <20181108.224633.1499859196570533612.mbj@tail-f.com> <a1bd7f74-19d6-c8bc-a34d-79ac0ac866e0@cisco.com>
X-Mailer: Mew version 6.7 on Emacs 25.2 / Mule 6.0 (HANACHIRUSATO)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/netmod/tS4GUmxwPDVjcskP1AP01Bx7tKE>
Subject: Re: [netmod] Fwd: New Version Notification for draft-verdt-netmod-yang-versioning-reqs-01.txt
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: Fri, 09 Nov 2018 13:42:06 -0000

Joe Clarke <jclarke@cisco.com> wrote:
> On 11/8/18 16:46, Martin Bjorklund wrote:
> > Hi,
> > 
> > After the session today, it seems to me that one fundamental
> > requirement (or non-requirement) is missing.  How much branching does
> > the solution have to support?  The current solution (6020/7950) and (if
> > I understood Rob Shakir correctly) also openconfig have linear
> > versioning *per module*.  If we can get agreement on this requirement,
> > I think it will be easier to find a solution.
> 
> We discussed this in the DT.  We didn't want to discuss levels of
> branching in the requirements as that pointed to certain solutions.

All requirements point to certain solutions, in a sense.

But if you say that branching is not a requirement on a solution, I'm
happy with that.

> The
> point of requirement 1.4 was to say that the DT felt previous versions
> of modules needed to support fixes without bringing in elements from head.

I think this means that you require branching.

But is this still the point of the "new 1.4" that was mentioned in the
session?

However, as Rob Shakir mentioned in the session, there are other ways
to do fixes / enhacements than branching a single module.  You can add
new functionality with augment and make changes with deviations.


/martin


> We discussed branching to satisfy this requirement as well as protecting
> new features with if-feature and using deviations.
> 
> Joe
>