Milestones and dates (was Re: New datatracker release: v6.116.0)
Adam Roach <adam@nostrum.com> Thu, 23 January 2020 16:13 UTC
Return-Path: <adam@nostrum.com>
X-Original-To: wgchairs@ietfa.amsl.com
Delivered-To: wgchairs@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 395551208A9 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2020 08:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.668
X-Spam-Level:
X-Spam-Status: No, score=-1.668 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, HTML_MESSAGE=0.001, T_KAM_HTML_FONT_INVALID=0.01, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
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 t_0Vpfxm6Su9 for <wgchairs@ietfa.amsl.com>; Thu, 23 Jan 2020 08:13:39 -0800 (PST)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CB65812089F for <wgchairs@ietf.org>; Thu, 23 Jan 2020 08:13:39 -0800 (PST)
Received: from Zephyrus.local (99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228]) (authenticated bits=0) by nostrum.com (8.15.2/8.15.2) with ESMTPSA id 00NGDaI3073667 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Thu, 23 Jan 2020 10:13:38 -0600 (CST) (envelope-from adam@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1579796018; bh=bVMkMbTiNKhbEplZxWpIt63AqmT+NWwQDYaP8KBtCOI=; h=Subject:To:References:From:Date:In-Reply-To; b=n4519V5fMgRHAdWmFOARYB7BCOfXxI3Y56dO4/+QZBW9Z6kWgrt1LA+YwXCbHOs2F OAhtWhM3Y2zGLpcHoVX/nbl1CCwX42gXCOade58v+6N4VnhBNGdh1Btcxc3V/9Fa3m OnnXPhHBCWyrYARPvRUZ9CmNC/uEcZsg4r+MJQoI=
X-Authentication-Warning: raven.nostrum.com: Host 99-152-146-228.lightspeed.dllstx.sbcglobal.net [99.152.146.228] claimed to be Zephyrus.local
Subject: Milestones and dates (was Re: New datatracker release: v6.116.0)
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>, "rjsparks@nostrum.com" <rjsparks@nostrum.com>, "wgchairs@ietf.org" <wgchairs@ietf.org>
References: <E1ipfpK-0002Gu-8D@zinfandel.tools.ietf.org> <a4ee6287-e147-8bcc-6205-09220b44f952@nostrum.com> <DB7PR07MB4572515CE60DAC87E491FD1995360@DB7PR07MB4572.eurprd07.prod.outlook.com>
From: Adam Roach <adam@nostrum.com>
Message-ID: <d6857aaa-f9b7-ed03-8803-ae5913b7298f@nostrum.com>
Date: Thu, 23 Jan 2020 10:13:31 -0600
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:60.0) Gecko/20100101 Thunderbird/60.9.1
MIME-Version: 1.0
In-Reply-To: <DB7PR07MB4572515CE60DAC87E491FD1995360@DB7PR07MB4572.eurprd07.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------5EB03B914F58A4683906C4FD"
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/GKTCAy5As7czqteM-MlhqIvL2Ig>
X-BeenThere: wgchairs@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Working Group Chairs <wgchairs.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wgchairs/>
List-Post: <mailto:wgchairs@ietf.org>
List-Help: <mailto:wgchairs-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wgchairs>, <mailto:wgchairs-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Jan 2020 16:13:41 -0000
Hi! Sorry for the confusion around the new datatracker feature that allows working groups to remove dates from milestones. The IESG's intention here is to run an experiment to evaluate what positive and negative impacts may result. Please note that the decision to remove dates from your milestones needs approval by your responsible area director, who will need to make such a change in the datatracker. If you're interested in doing so, please start a conversation with your area director. If you have any feedback about this new functionality and its impact -- either beneficial or detrimental -- please send comments to the IESG. Thanks. /a On 1/16/20 03:28, Magnus Westerlund wrote: > > Hi WG Chairs, > > Please note that IESG would like to provide some guidance on when it > is suitable to exclude the dates. > > One reasons for this need is that RFC 2418 do have requirements on > charter and milestones: > > Goals and milestones > > The working group charter MUST establish a timetable for specific > > work items. While this may be renegotiated over time, the list of > > milestones and dates facilitates the Area Director's tracking of > > working group progress and status, and it is indispensable to > > potential participants identifying the critical moments for input. > > Milestones shall consist of deliverables that can be qualified as > > showing specific achievement; e.g., "Internet-Draft finished" is > > fine, but "discuss via email" is not. It is helpful to specify > > milestones for every 3-6 months, so that progress can be gauged > > easily. This milestone list is expected to be updated > > periodically (see section 5). > > So please await guidance. IESG will discuss this in our informal > telechat today. > > Cheers > > Magnus Westerlund > > TSV AD > > *From:*WGChairs <wgchairs-bounces@ietf.org> *On Behalf Of *Robert Sparks > *Sent:* den 15 januari 2020 23:26 > *To:* IETF WG Chairs <wgchairs@ietf.org> > *Subject:* Fwd: New datatracker release: v6.116.0 > > Chairs and ADs: > > This release brings the ability to configure a working group to manage > its milestones as an ordered list without dates. > > If you want to switch your group(s) over, see the "Edit milestones" > page for the group. > > If you try it and don't like it, you can switch back to using dates at > any time. > > Let me know if you run into problems or have any questions. > > RjS > > > > -------- Forwarded Message -------- > > *Subject: * > > > > New datatracker release: v6.116.0 > > *Date: * > > > > Thu, 09 Jan 2020 13:58:50 -0800 > > *From: * > > > > Henrik Levkowetz <henrik@levkowetz.com> <mailto:henrik@levkowetz.com> > > *To: * > > > > codesprints@ietf.org <mailto:codesprints@ietf.org>, iesg@ietf.org > <mailto:iesg@ietf.org>, wgchairs@ietf.org <mailto:wgchairs@ietf.org> > > > > > Hi, > > This is an automatic notification about a new datatracker release, > v6.116.0, generated when running the mkrelease script. > > Release notes: > > ietfdb (6.116.0) ietf; urgency=medium > > **Dateless group milestones, improved author stats, and bugfixes** > > * Merged in [17196] from rcross@amsl.com <mailto:rcross@amsl.com>: > Removed agenda@ietf.org <mailto:agenda@ietf.org> from audio import > notification To: list. > * Merged in [17195] from rcross@amsl.com <mailto:rcross@amsl.com>: > Updated admin permissions to grant secretariat access to > LiaisonStatementGroupContacts. > * Merged in [17185] from rjsparks@nostrum.com > <mailto:rjsparks@nostrum.com>: > Added support for dateless milestones. Fixes issue #2799. > > * Specified explicit UTF-8 decoding of submission checker output, in > order to avoid issues when reporting errors due to UTF-8 content. > > * Merged in [17181] from olau@iola.dk <mailto:olau@iola.dk>: > Fixed a problem with assignments to the same session causing a crash. > * Merged in [17179] from housley@vigilsec.com > <mailto:housley@vigilsec.com>: > Added references and referened-by buttons to each RFC listed on the person > profile page. In addition, changed the buttons on the document references > and document referenced-by pages to match the buttons on the main document > page (the buttons with the long arrows). Fixes #2854, although it does not > include the number of references in the button. > > * Merged in [17178] from housley@vigilsec.com > <mailto:housley@vigilsec.com>: > Turned text names into links on the stats pages. Fixes issue #2854. > > * Refactored some document methods to align better with Django's > get_absolute_url(), and added Person.get_absolute_uri() > > * Merged in [17177] from rjsparks@nostrum.com > <mailto:rjsparks@nostrum.com>: > Improve can_ballot. Fixes #2856. > > * Limited the permitted versions of mypy and related django-slugs, to > avoid > issues related to using Django-1.11. We should update to latest versions > when we've moved to Django 2.2.x > > * Changed ReviewerSettings history change-reason field to be a > TextField, in > order to accomodate longer change descriptions. > > * Merged in [17173] from rjsparks@nostrum.com > <mailto:rjsparks@nostrum.com>: > Worked around a problem with displaying IESG evaluation information > for non-approve ballot types. Partially addresses #2851. > -- Henrik Levkowetz <henrik@levkowetz.com> > <mailto:henrik@levkowetz.com> 09 Jan 2020 18:31:03 +0000 > > The new version is available for installation through SVN checkout, with > 'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.116.0' > > For development, copy the new development version instead: > 'svn copy > https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.116.1.dev0' > <YOURBRANCH> > > Regards, > > Henrik > (via the mkrelease script) >
- New datatracker release: v6.116.0 Henrik Levkowetz
- Fwd: New datatracker release: v6.116.0 Robert Sparks
- RE: New datatracker release: v6.116.0 Magnus Westerlund
- Milestones and dates (was Re: New datatracker rel… Adam Roach
- Re: Milestones and dates (was Re: New datatracker… Mark Nottingham
- Re: Milestones and dates (was Re: New datatracker… Adam Roach