RE: New datatracker release: v6.98.0

Tianran Zhou <zhoutianran@huawei.com> Mon, 17 June 2019 01:28 UTC

Return-Path: <zhoutianran@huawei.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 BA261120108; Sun, 16 Jun 2019 18:28:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 cY2bQWMH1Q_S; Sun, 16 Jun 2019 18:28:39 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 399521200FD; Sun, 16 Jun 2019 18:28:39 -0700 (PDT)
Received: from lhreml704-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 78D671AB869A7B010CFD; Mon, 17 Jun 2019 02:28:36 +0100 (IST)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml704-cah.china.huawei.com (10.201.108.45) with Microsoft SMTP Server (TLS) id 14.3.408.0; Mon, 17 Jun 2019 02:28:34 +0100
Received: from NKGEML515-MBX.china.huawei.com ([fe80::a54a:89d2:c471:ff]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0415.000; Mon, 17 Jun 2019 09:28:25 +0800
From: Tianran Zhou <zhoutianran@huawei.com>
To: Henrik Levkowetz <henrik@levkowetz.com>, "codesprints@ietf.org" <codesprints@ietf.org>, "iesg@ietf.org" <iesg@ietf.org>, "wgchairs@ietf.org" <wgchairs@ietf.org>
Subject: RE: New datatracker release: v6.98.0
Thread-Topic: New datatracker release: v6.98.0
Thread-Index: AQHVJE63F+IEPlskl0K6dn3Un4REuaafDmXw
Date: Mon, 17 Jun 2019 01:28:24 +0000
Message-ID: <BBA82579FD347748BEADC4C445EA0F21BEE3D90A@NKGEML515-MBX.china.huawei.com>
References: <E1hcW19-0001a0-A4@zinfandel.tools.ietf.org>
In-Reply-To: <E1hcW19-0001a0-A4@zinfandel.tools.ietf.org>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.156.116]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/wgchairs/ObTeG4DWbcn1ngPkFVMwnZT92xE>
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: Mon, 17 Jun 2019 01:28:42 -0000

Hi Henrik,

I cannot see the individual drafts from the WG data tracker, i.e., only RFCs and WG documents. For example:
https://datatracker.ietf.org/wg/opsawg/documents/

Does this caused by the latest release?

Regards,
Tianran

> -----Original Message-----
> From: WGChairs [mailto:wgchairs-bounces@ietf.org] On Behalf Of Henrik
> Levkowetz
> Sent: Sunday, June 16, 2019 10:20 PM
> To: codesprints@ietf.org; iesg@ietf.org; wgchairs@ietf.org
> Subject: New datatracker release: v6.98.0
> 
> 
> Hi,
> 
> This is an automatic notification about a new datatracker release, v6.98.0,
> generated when running the mkrelease script.
> 
> Release notes:
> 
> ietfdb (6.98.0) ietf; urgency=medium
> 
>   **Refactoring of the primary index type for Document and DocAlias objects**
> 
>   This release contains a series of 216 migration steps that changes the
>   Document and DocAlias primary keys from character strings to integers, and
>   makes corresponding code changes.
> 
>   This was prompted by database limitations discovered when trying to make
>   DocAlias use a m2m document field; with 255 long strings as primary keys
> for
>   Document and DocAlias this violated the MySQL database limitations.
> 
>   Changing the primary keys to integers should also improve efficiency.
> 
>   Additionally, in order to make it possible to have DocAlias objects
> referring
>   to multiple documents, in order to reflect STD and BCP names that refer
> to
>   multiple RFCs, DocAlias has been refactored to use many-to-many tables
> instead
>   of foreign keys do toduments.
> 
>   Due to the data migrations which create the new integer primary keys and
> adds
>   corresponding integer foreign keys matching the previous string foreign
> keys
>   in all tables having foreign keys to Document and DocAlias, some of these
>   migrations take a long time.  The total set of migrations are expected to
> have
>   a runtime on the order of 2 hours.
> 
>   This release is scheduled to be deployed on 16 Jun 2019 at 16:00 UTC, with
>   an expected datatracker downtime, for safety backup and application of the
>   migrations to run, of about 3 hours.
> 
>  -- Henrik Levkowetz <henrik@levkowetz.com>  16 Jun 2019 14:16:12 +0000
> 
> The new version is available for installation through SVN checkout, with
>   'svn checkout https://svn.tools.ietf.org/svn/tools/ietfdb/tags/6.98.0'
> 
> For development, copy the new development version instead:
>   'svn copy
> https://svn.tools.ietf.org/svn/tools/ietfdb/tags/dev/6.98.1.dev0'
> <YOURBRANCH>
> 
> Regards,
> 
> 	Henrik
> 	(via the mkrelease script)