qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: John Snow <jsnow@redhat.com>, qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Markus Armbruster <armbru@redhat.com>,
	Michael Roth <michael.roth@amd.com>,
	Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH v2 1/2] Python: bump minimum sphinx version to 3.4.3
Date: Wed, 3 Jul 2024 20:35:16 +0200	[thread overview]
Message-ID: <521d36b0-faf9-41b3-b324-879e24f2905f@redhat.com> (raw)
In-Reply-To: <20240703175235.239004-2-jsnow@redhat.com>

On 03/07/2024 19.52, John Snow wrote:
> With RHEL 8 support retired (It's been two years since RHEL9 released),
> our very oldest build platform version of Sphinx is now 3.4.3; and
> keeping backwards compatibility for versions as old as v1.6 when using
> domain extensions is a lot of work we don't need to do.
> 
> This patch is motivated by my work creating a new QAPI domain, which
> unlike the dbus documentation, cannot be allowed to regress by creating
> a "dummy" doc when operating under older sphinx versions. Easier is to
> raise our minimum version as far as we can push it forwards, reducing my
> burden in creating cross-compatibility hacks and patches.
> 
> A sampling of sphinx versions from various distributions, courtesy
> https://repology.org/project/python:sphinx/versions
> 
> Alpine 3.16: v4.3.0 (QEMU support ended 2024-05-23)
> Alpine 3.17: v5.3.0
> Alpine 3.18: v6.1.3
> Alpine 3.19: v6.2.1
> Ubuntu 20.04 LTS: EOL
> Ubuntu 22.04 LTS: v4.3.2
> Ubuntu 22.10: EOL
> Ubuntu 23.04: EOL
> Ubuntu 23.10: v5.3.0
> Ubuntu 24.04 LTS: v7.2.6
> Debian 11: v3.4.3 (QEMU support ends 2024-07-xx)
> Debian 12: v5.3.0
> Fedora 38: EOL
> Fedora 39: v6.2.1
> Fedora 40: v7.2.6
> CentOS Stream 8: v1.7.6 (QEMU support ended 2024-05-17)
> CentOS Stream 9: v3.4.3
> OpenSUSE Leap 15.4: EOL
> OpenSUSE Leap 15.5: 2.3.1, 4.2.0 and 7.2.6
> 
> RHEL9 / CentOS Stream 9 becomes the new defining factor in staying at
> Sphinx 3.4.3 due to downstream offline build requirements that force us
> to use platform Sphinx instead of newer packages from PyPI.
> 
> Signed-off-by: John Snow <jsnow@redhat.com>
> Acked-by: Paolo Bonzini <pbonzini@redhat.com>
> Acked-by: Markus Armbruster <armbru@redhat.com>
> ---
>   docs/conf.py    | 7 +++----
>   pythondeps.toml | 2 +-
>   2 files changed, 4 insertions(+), 5 deletions(-)

Reviewed-by: Thomas Huth <thuth@redhat.com>




  reply	other threads:[~2024-07-03 18:36 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-03 17:52 [PATCH v2 0/2] docs/python: bump minimum Sphinx version John Snow
2024-07-03 17:52 ` [PATCH v2 1/2] Python: bump minimum sphinx version to 3.4.3 John Snow
2024-07-03 18:35   ` Thomas Huth [this message]
2024-07-03 17:52 ` [PATCH v2 2/2] docs: remove Sphinx 1.x compatibility code John Snow
2024-07-03 18:38   ` Thomas Huth
2024-07-05 15:50 ` [PATCH v2 0/2] docs/python: bump minimum Sphinx version John Snow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=521d36b0-faf9-41b3-b324-879e24f2905f@redhat.com \
    --to=thuth@redhat.com \
    --cc=armbru@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=michael.roth@amd.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).