Re: [Tools-discuss] New datatracker milestone feature (Fwd: [core] Milestones changed for core WG)

Ole Laursen <olau@iola.dk> Tue, 18 June 2013 12:43 UTC

Return-Path: <olau@iola.dk>
X-Original-To: tools-discuss@ietfa.amsl.com
Delivered-To: tools-discuss@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B480221F9ED0 for <tools-discuss@ietfa.amsl.com>; Tue, 18 Jun 2013 05:43:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.978
X-Spam-Level:
X-Spam-Status: No, score=-1.978 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ahFf3R3k5wTC for <tools-discuss@ietfa.amsl.com>; Tue, 18 Jun 2013 05:43:03 -0700 (PDT)
Received: from mail-ve0-x22f.google.com (mail-ve0-x22f.google.com [IPv6:2607:f8b0:400c:c01::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 1F07721F9ECD for <tools-discuss@ietf.org>; Tue, 18 Jun 2013 05:43:02 -0700 (PDT)
Received: by mail-ve0-f175.google.com with SMTP id da11so3022095veb.20 for <tools-discuss@ietf.org>; Tue, 18 Jun 2013 05:43:02 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding:x-gm-message-state; bh=QjBR7xscnymW1ghapqKNppI6kSC/uy330Sd9BL7S48c=; b=iu/PwEdHNXh0RVraKoOOxcnAciJcD15bn0dU0SkX/b2GJ/XIIDEuZbxiACrZNN/2y0 RTEFR2vxuDhuPIMCzbg+5a/H5P0tGfvUK2N+tGSSLwmJ5YNhIeVv5dnupTm+vQr+0i3B wz8GAOfUSv3/nDeNGEZdqrC5i5FbRXWaQlvsoC/LTPo6I+XSmYgciXyrRbiXGqxJhi7O Vz0hpxf5XB98eP2pgucnov/zE3kJvTSEuKlVQBkpZn6eZOFncNxozAIUSfOpo/owZ701 kGwtAhVxDN/DKPo5GHj4ITC25icjC1xQ1C0ZgdRFgnc2KOrf4AP5t6q35JOvkorzJgdw 82tg==
X-Received: by 10.52.103.99 with SMTP id fv3mr1485836vdb.11.1371559382012; Tue, 18 Jun 2013 05:43:02 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.58.133.71 with HTTP; Tue, 18 Jun 2013 05:42:41 -0700 (PDT)
In-Reply-To: <CANb2Ov+XTFYHmjpg2VHFUs29D_zoSb2A+r+FFrS7FjBzm_zsqQ@mail.gmail.com>
References: <20130520234121.29152.96315.idtracker@ietfa.amsl.com> <0D6B8765-0B8F-4937-B086-291DBC2E2277@tzi.org> <CANb2Ov+XTFYHmjpg2VHFUs29D_zoSb2A+r+FFrS7FjBzm_zsqQ@mail.gmail.com>
From: Ole Laursen <olau@iola.dk>
Date: Tue, 18 Jun 2013 14:42:41 +0200
Message-ID: <CANb2OvKG5yubE4gJj0uq4KzuR6m-4Af7GUA+bocEetL6Dzt9Sg@mail.gmail.com>
To: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Gm-Message-State: ALoCoQk3r4T/EzXtfAR/07jDSd4uicy+PKbW8Dvmb3UQdmjWyQSvBRXDKOPacm9nMf29l1quhEol
Cc: "tools-discuss@ietf.org Discussion" <tools-discuss@ietf.org>
Subject: Re: [Tools-discuss] New datatracker milestone feature (Fwd: [core] Milestones changed for core WG)
X-BeenThere: tools-discuss@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF Tools Discussion <tools-discuss.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/tools-discuss>
List-Post: <mailto:tools-discuss@ietf.org>
List-Help: <mailto:tools-discuss-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tools-discuss>, <mailto:tools-discuss-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Jun 2013 12:43:03 -0000

I think this is comes from a relatively late change we did to the
milestones to work in terms of months and years only, and not
individual dates.

So what happens is that some of the existing milestones are actually
on a specific date, whereas the parsed output hardcodes the date to
the last day of the month. So when comparing the actual values, there
is in fact a change which is duly reported (but too little precision
to enable you to see it).

In other words, we need to get the existing milestones due dates fixed
to be at the last day of the month.

Ole

2013/5/21 Ole Laursen <olau@iola.dk>:
> Hm, right, that looks like a bug. I'll take a look.
>
>
> Ole
>
> 2013/5/21 Carsten Bormann <cabo@tzi.org>:
>> Great new feature!  Finally milestones have a chance to stay current.
>>
>> One suggestion for the notification;
>> Maybe don't record a change where nothing has changed?
>> (All the "set due date" ones.)
>>
>> Grüße, Carsten
>>
>>
>> Begin forwarded message:
>>
>>> From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
>>> Subject: [core] Milestones changed for core WG
>>> Date: May 21, 2013 01:41:21 +0200
>>> To: core@ietf.org
>>>
>>> Changed milestone "CoAP protocol specification with mapping to HTTP
>>> Rest API submitted to IESG as PS", set due date to December 2012 from
>>> December 2012, resolved as "Done", added draft-ietf-core-coap to
>>> milestone.
>>>
>>> Changed milestone "Blockwise transfers in CoAP submitted to IESG", set
>>> due date to February 2013 from February 2013.
>>>
>>> Changed milestone "Observing Resources in CoAP submitted to IESG", set
>>> due date to February 2013 from February 2013.
>>>
>>> Changed milestone "Group Communication for CoAP submitted to IESG",
>>> set due date to April 2013 from April 2013.
>>>
>>> Changed milestone "HOLD (date TBD) Constrained security bootstrapping
>>> specification submitted to IESG", set due date to December 2099 from
>>> December 2099.
>>>
>>> URL: http://datatracker.ietf.org/wg/core/charter/
>>> _______________________________________________
>>> core mailing list
>>> core@ietf.org
>>> https://www.ietf.org/mailman/listinfo/core
>>>
>>
>> _______________________________________________
>> Tools-discuss mailing list
>> Tools-discuss@ietf.org
>> https://www.ietf.org/mailman/listinfo/tools-discuss