Re: [Rfc-markdown] [xml2rfc-dev] New xml2rfc release: v3.8.0
Robert Sparks <rjsparks@nostrum.com> Mon, 14 June 2021 15:50 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: rfc-markdown@ietfa.amsl.com
Delivered-To: rfc-markdown@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 82D873A28BD; Mon, 14 Jun 2021 08:50:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.08
X-Spam-Level:
X-Spam-Status: No, score=-2.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) 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 yFWkUlMu1Dc9; Mon, 14 Jun 2021 08:50:28 -0700 (PDT)
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 20F5C3A28BB; Mon, 14 Jun 2021 08:50:28 -0700 (PDT)
Received: from unformal.localdomain ([47.186.34.206]) (authenticated bits=0) by nostrum.com (8.16.1/8.16.1) with ESMTPSA id 15EFoQ3H084230 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 14 Jun 2021 10:50:27 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1623685827; bh=vuZB6MUtS4uAqoHY19ooU8zCF22iqs4xfChi7E7yeR4=; h=Subject:From:To:Cc:References:Date:In-Reply-To; b=WoyrqrkqAmsRCn+7FQFtbqJjm7FwSEMPLkqiENl46Em32oM6R6bBAOdn9aZXAz/IO m5y8AmxTSgBSYmyU1y7BXX6SraUbC4RDRvDNB+GhVOmUav/JtfVlJRItt8/NMYJ+H9 E47kEVBxOS1vwADy3TG7ulLyQc4l9hHBAXu/Xb0g=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.34.206] claimed to be unformal.localdomain
From: Robert Sparks <rjsparks@nostrum.com>
To: xml2rfc-dev@ietf.org, xml2rfc@ietf.org
Cc: rfc-markdown@ietf.org
References: <E1lsomg-00003x-J4@84d908c3c732>
Message-ID: <41b0c340-9964-4d10-c8af-ee1bad48dde5@nostrum.com>
Date: Mon, 14 Jun 2021 10:50:21 -0500
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:78.0) Gecko/20100101 Thunderbird/78.11.0
MIME-Version: 1.0
In-Reply-To: <E1lsomg-00003x-J4@84d908c3c732>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/bOlaHXmjH5guNp9Gr50HmeilETg>
Subject: Re: [Rfc-markdown] [xml2rfc-dev] New xml2rfc release: v3.8.0
X-BeenThere: rfc-markdown@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "rfc-markdown is a discussion list for people writing I-Ds and RFCs in Markdown and the authors of the tools used for that." <rfc-markdown.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-markdown/>
List-Post: <mailto:rfc-markdown@ietf.org>
List-Help: <mailto:rfc-markdown-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rfc-markdown>, <mailto:rfc-markdown-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 Jun 2021 15:50:33 -0000
This is a delayed message - 3.8.0 has been out for a bit, but the announcement message to these lists failed to be sent. It's here now so that it is in the archives. RjS On 6/14/21 10:45 AM, rjsparks@nostrum.com wrote: > Hi, > > This is an automatic notification about a new xml2rfc release, > v3.8.0, generated when running the mkrelease script. > > Release notes: > > xml2rfc (3.8.0) ietf; urgency=medium > > * Merged in [3961] from jennifer@painless-security.com: > Fix indentation error that prevented normalizing ascii-art whitespace. > Fixes #403. > > * Merged in [3949] from jennifer@painless-security.com: > Insert removeInRFC notice as first child even when <name> tag is absent. > Fixes #622. > > * Merged in [3947] from jennifer@painless-security.com: > Handle <iref> as child of most of its allowed parent elements. > An <aside> parent is still not handled properly. Fixes #620. > > * Merged in [3942] from jennifer@painless-security.com: > Refer to un-numbered sections by name rather than number. > Fixes #572. > > * Merged in [3939] and [3940] from jennifer@painless-security.com: > Create tests-no-network and clear-cache Makefile targets to support > network-free testing. Updates to tests/cache and tests/valid so > tests pass with and without network. Fixes #561. > > -- Robert Sparks <rjsparks@nostrum.com> 20 May 2021 18:05:43 +0000 > > The preferred way to install xml2rfc is by doing 'pip install xml2rfc', > and 'pip install --upgrade xml2rfc' to upgrade. If there are system- > installed python modules which pip will not upgrade, you may have to > use 'pip install --upgrade --no-deps xml2rfc' and install dependencies > manually. > > The new version is also available through SVN checkout, with > 'svn checkout https://svn.ietf.org/svn/tools/xml2rfc/tags/cli/3.8.0' > > Documentation for this release is built-in, and also available at: > https://xml2rfc.tools.ietf.org/xml2rfc-doc-3.8.0.html > > Regards, > > Robert Sparks > (via the mkrelease script) > > _______________________________________________ > xml2rfc-dev mailing list > xml2rfc-dev@ietf.org > https://www.ietf.org/mailman/listinfo/xml2rfc-dev
- [Rfc-markdown] New xml2rfc release: v3.8.0 rjsparks
- Re: [Rfc-markdown] [xml2rfc-dev] New xml2rfc releā¦ Robert Sparks