Re: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker

Roman Danyliw <> Thu, 16 May 2019 17:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 90846120117 for <>; Thu, 16 May 2019 10:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id PBt-yJ5GBGI3 for <>; Thu, 16 May 2019 10:45:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C1B37120025 for <>; Thu, 16 May 2019 10:45:03 -0700 (PDT)
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id x4GHj14u011326; Thu, 16 May 2019 13:45:01 -0400
DKIM-Filter: OpenDKIM Filter v2.11.0 x4GHj14u011326
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=yc2bmwvrj62m; t=1558028701; bh=5y6hRTXE/HbnQ4ZLHRCgN7p5yzhpnSkB5uCbsQDiGnk=; h=From:To:CC:Subject:Date:References:In-Reply-To:From; b=TDvgkIKgfzm9P/b+vFjzcTS7ozswFpBVfJRrhc8cUjxaN7MQkzTxjH+ABJQ64Alfl Ay3jXFWlLzzJDRa7EyMpdMjpCbyB4pUOd++s9owfP3uWwdnpvZzhiIRIXyJf1oaRZy SfPaYsygleGZLYG04dBGWGXZBqOKMEtUjtu7gZqI=
Received: from ( []) by (8.14.7/8.14.7) with ESMTP id x4GHj0SQ032326; Thu, 16 May 2019 13:45:00 -0400
Received: from ([]) by ([]) with mapi id 14.03.0439.000; Thu, 16 May 2019 13:45:00 -0400
From: Roman Danyliw <>
To: Robert Sparks <>, "" <>
Thread-Topic: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker
Thread-Index: AdUBEuo4FoCGVhV0SFan06BVl/vCxgLAYo+AAAMB8QAABPWGIA==
Date: Thu, 16 May 2019 17:44:59 +0000
Message-ID: <359EC4B99E040048A7131E0F4E113AFC01B336955F@marathon>
References: <359EC4B99E040048A7131E0F4E113AFC01B3367E08@marathon> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_359EC4B99E040048A7131E0F4E113AFC01B336955Fmarathon_"
MIME-Version: 1.0
Archived-At: <>
Subject: Re: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Tools Development list server <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 16 May 2019 17:45:09 -0000

Ack.  Thanks for finding the code and the tickets. seems to be the related issue/enhancement.

I'll talk it through with them, but the interest was around the following states:

"AD Evaluation::AD Followup"
"AD Evaluation::Revised I-D Needed"
"IESG Evaluation::Revised I-D Needed"
"IESG Evaluation::AD Followup"

Per the question of metrics and motivation, (one of the) identified drivers was to implicitly distinguish between waiting on document authors (Revised ID Needed) vs. waiting on AD/IESG (AD Followup)

I'll get back to you,

From: TOOLS-DEVELOPMENT [] On Behalf Of Robert Sparks
Sent: Thursday, May 16, 2019 11:50 AM
Subject: Re: [TOOLS-DEVELOPMENT] How do counters reset in the datatracker

So the direct answer is simpler than I expected. It is the last change in iesg state (or the date iesg-evaluation started).

The relevant code is here:

at line 168.


On 5/16/19 9:23 AM, Robert Sparks wrote:

Hi Roman -

Like Russ, I will have to look at the code to give you the exact answer you are looking for, and I hope to do that today or tomorrow. I fear the answer will be "it's complicated".

For the moment, I can point to some history. Different ADs over time have had different opinions about what these "since" values should represent. Should it show time since last action, or accrued time in the where it is in the queue? Who is the metric there to help push along? I've occasionally been of the opinion that perhaps we should show state and sub-state staleness separately (as suggested by Adrian in one of the tickets below), but the display does get cluttered...


<><> and



On 5/16/19 8:31 AM, Roman Danyliw wrote:


At the IESG retreat, there was a confusion in the IESG about how the timer listed next to the draft  (e.g., "for xxx days") in the datatracker is reset when a state or sub-state changes (see screenshot).  I was asked get clarity on the following:

** Which sub-state changes will trigger a reset to 0?

** Which state changes will trigger a reset to 0?




TOOLS-DEVELOPMENT mailing list<>


TOOLS-DEVELOPMENT mailing list<>