[Rfc-markdown] Versions

Carsten Bormann <cabo@tzi.org> Thu, 26 January 2023 18:11 UTC

From: Carsten Bormann <cabo@tzi.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
Date: Thu, 26 Jan 2023 19:11:02 +0100
Message-Id: <C2737FDA-AEEC-405D-8500-1BAA6E46288F@tzi.org>
To: rfc-markdown@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-markdown/V_sVdZn-MhMshPjol2U8RUVXOho>
Subject: [Rfc-markdown] Versions
Precedence: list

For a different tool (cddlc), I needed some estimate of which Ruby versions IETFers are using.  Obviously, the audience of cddlc and kramdown-rfc are going to be different, but for the latter we get artifacts that have version numbers in them…

So, in the last 100 days, some 478 drafts have been submitted with XML that says they were generated by kramdown-rfc.  The Ruby versions under which these were run are (*):

  75 old enough kramdown-rfc to not show the Ruby version
  12 Ruby 2.3
   7 Ruby 2.5
  68 Ruby 2.6
  21 Ruby 2.7
 121 Ruby 3.0
 171 Ruby 3.1
   4 Ruby 3.2

So about 80 % of kramdown-rfc-generated drafts where we know the version, used a “modern” (≥ 2.7) version of Ruby.
Good, because in cddlc I planned to use features of 3.0 that already had provisional support in 2.7, and I think I’ll now go ahead with this.
(Kramdown-rfc itself will probably stay at a minimum requirement of Ruby 2.3 a little longer, but will probably gradually experience bitrot in the libraries that come with that.)

I was surprised by the number of drafts generated still using pre-2.6 versions of Ruby (which would, e.g., imply a 2018 or earlier operating system on a Mac); these should really be gone now.
I also was surprised by the ancient kramdown-rfc versions in use:

  11 version 1.2.3 June 02, 2017
   7 version 1.4.1 March 22, 2021
   8 version 1.5.12 October 20, 2021

2017!

Folks, please do update your kramdown-rfc versions occasionally (preferably after going to a modern version of Ruby first, but please don’t procrastinate for that):

  gem update kramdown-rfc

(If you are pre-1.6.1, i.e., < February 21, 2022, do a `gem update kramdown-rfc2629` before and then a `gem install kramdown-rfc`.)

The reason for really wanting an update is that the world has changed since 2017 (RFCXMLv3, bib.ietf.org, …), and kramdown-rfc needs to interact with that.

Grüße, Carsten

(*) No, I don’t know why these don’t add up; I just need rough numbers and won’t look.

[Rfc-markdown] Versions Carsten Bormann