Re: [NGO] external module properties

Martin Bjorklund <mbj@tail-f.com> Tue, 29 April 2008 19:48 UTC

Return-Path: <ngo-bounces@ietf.org>
X-Original-To: ngo-archive@optimus.ietf.org
Delivered-To: ietfarch-ngo-archive@core3.amsl.com
Received: from core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 2755F28C1EC; Tue, 29 Apr 2008 12:48:17 -0700 (PDT)
X-Original-To: ngo@core3.amsl.com
Delivered-To: ngo@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 210B728C1EC for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 12:48:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.495
X-Spam-Level:
X-Spam-Status: No, score=-0.495 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, HELO_MISMATCH_COM=0.553, RDNS_NONE=0.1]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lDVCc+XfQsGQ for <ngo@core3.amsl.com>; Tue, 29 Apr 2008 12:48:10 -0700 (PDT)
Received: from mail.tail-f.com (unknown [213.180.94.162]) by core3.amsl.com (Postfix) with ESMTP id B279B3A6AC4 for <ngo@ietf.org>; Tue, 29 Apr 2008 12:48:10 -0700 (PDT)
Received: from localhost (c213-100-166-13.swipnet.se [213.100.166.13]) by mail.tail-f.com (Postfix) with ESMTP id AF4C31B80D2; Tue, 29 Apr 2008 21:48:12 +0200 (CEST)
Date: Tue, 29 Apr 2008 21:48:10 +0200
Message-Id: <20080429.214810.13543341.mbj@tail-f.com>
To: phil@juniper.net
From: Martin Bjorklund <mbj@tail-f.com>
In-Reply-To: <200804291905.m3TJ5ewb090087@idle.juniper.net>
References: <sdve20sdgi.fsf@wes.hardakers.net> <200804291905.m3TJ5ewb090087@idle.juniper.net>
X-Mailer: Mew version 5.2.52 on Emacs 22.1 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Cc: ngo@ietf.org
Subject: Re: [NGO] external module properties
X-BeenThere: ngo@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: NETCONF Goes On - discussions on future work and extensions to NETCONF <ngo.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ngo>
List-Post: <mailto:ngo@ietf.org>
List-Help: <mailto:ngo-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ngo>, <mailto:ngo-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ngo-bounces@ietf.org
Errors-To: ngo-bounces@ietf.org

Hi,

Phil Shafer <phil@juniper.net> wrote:
> There's a lot to be gained by using dates and not a lot of down
> side.  Being able to look at the revision history and see when what
> happened, how stable a module is, and how likely folks are to be
> up-to-date with the latest version is important.  And it avoids
> tons of discussion about whether we need two or three decimal numbers
> and when the major or minor version should change.  It's simple,
> obvious, sortable, well-defined, and will last for thousands of
> years.

I fully agree with this.

How about adding an optional counter after the date?  So you can do

  2008-04-29
  2008-04-29:1
  2008-04-29:2

and so on.

It removes the arbitrary timing constraint that worries Wes, and it's
still simple enough for the common use case.


/martin

  
_______________________________________________
NGO mailing list
NGO@ietf.org
https://www.ietf.org/mailman/listinfo/ngo