qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Eduardo Habkost" <eduardo@habkost.net>,
	"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	"Zhao Liu" <zhao1.liu@intel.com>,
	"Yanan Wang" <wangyanan55@huawei.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/4] docs: automated info about machine deprecation/removal info
Date: Tue, 25 Feb 2025 20:04:19 +0000	[thread overview]
Message-ID: <20250225200423.2350471-1-berrange@redhat.com> (raw)

Since we deprecate and remove versioned machine types on a fixed
schedule, we can automatically ensure that the docs reflect the
latest version info, rather than requiring manual updates on each
dev cycle.

The first patch in this series fixes the logic to ensure dev snapshots
and release candidates don't have an off-by-1 error in setting
deprecation and removal thresholds - they must predict the next formal
release version number.

The remaining patches deal with the docs stuff.

The first two patches can be applied in this release (10.0) if desired.

The third patch documents deletion logic that doesn't come into effect
until the 10.1.0 release is out, so we shouldn't include that commit
in 10.0.0. It can be applied after the following is reverted:

  commit c9fd2d9a48ee3c195cf83cc611b87b09f02f0013
  Author: Daniel P. Berrangé <berrange@redhat.com>
  Date:   Thu Jun 20 17:57:37 2024 +0100

    include/hw: temporarily disable deletion of versioned machine types

    The new deprecation and deletion policy for versioned machine types is
    being introduced in QEMU 9.1.0.

    Under the new policy a number of old machine types (any prior to 2.12)
    would be liable for immediate deletion which would be a violation of our
    historical deprecation and removal policy

    Thus automatic deletions (by skipping QOM registration) are temporarily
    gated on existance of the env variable "QEMU_DELETE_MACHINES" / QEMU
    version number >= 10.1.0. This allows opt-in testing of the automatic
    deletion logic, while activating it fully in QEMU >= 10.1.0.

    This whole commit should be reverted in the 10.1.0 dev cycle or shortly
    thereafter.

Daniel P. Berrangé (4):
  include/hw/boards: cope with dev/rc versions in deprecation checks
  docs/about/deprecated: auto-generate a note for versioned machine
    types
  docs/about/removed-features: auto-generate a note for versioned
    machine types
  include/hw/boards: add warning about changing deprecation logic

 docs/about/deprecated.rst       |  7 ++++++
 docs/about/removed-features.rst | 10 +++++----
 docs/conf.py                    | 39 ++++++++++++++++++++++++++++++++-
 include/hw/boards.h             | 39 +++++++++++++++++++++++++++++++--
 4 files changed, 88 insertions(+), 7 deletions(-)

-- 
2.47.1



             reply	other threads:[~2025-02-25 20:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-25 20:04 Daniel P. Berrangé [this message]
2025-02-25 20:04 ` [PATCH 1/4] include/hw/boards: cope with dev/rc versions in deprecation checks Daniel P. Berrangé
2025-02-25 20:04 ` [PATCH 2/4] docs/about/deprecated: auto-generate a note for versioned machine types Daniel P. Berrangé
2025-02-25 20:15   ` Thomas Huth
2025-02-25 20:04 ` [PATCH 3/4] docs/about/removed-features: " Daniel P. Berrangé
2025-02-25 20:17   ` Thomas Huth
2025-02-25 20:04 ` [PATCH 4/4] include/hw/boards: add warning about changing deprecation logic Daniel P. Berrangé
2025-02-25 20:19   ` Thomas Huth

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=20250225200423.2350471-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=wangyanan55@huawei.com \
    --cc=zhao1.liu@intel.com \
    /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).