qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
	"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
	"Yanan Wang" <wangyanan55@huawei.com>,
	"John Snow" <jsnow@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Thomas Huth" <thuth@redhat.com>,
	devel@lists.libvirt.org,
	"Peter Maydell" <peter.maydell@linaro.org>,
	"Eduardo Habkost" <eduardo@habkost.net>,
	"Zhao Liu" <zhao1.liu@intel.com>
Subject: Re: [PATCH v2 0/5] docs: automated info about machine deprecation/removal info
Date: Sun, 11 May 2025 14:24:41 -0400	[thread overview]
Message-ID: <20250511142433-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20250429131526.1842130-1-berrange@redhat.com>

On Tue, Apr 29, 2025 at 02:15:21PM +0100, Daniel P. Berrangé wrote:
> 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 removes the hack which postponed
> automatic removal of versioned machine types to the 10.1.0 release,
> since we're now in the 10.1.0 dev cycle.
> 
> The second 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 following three patches deal with the docs stuff.
> 
> With this series applied all versioned machine types prior to 4.1
> are now removed (hidden). We can delete the code at our leisure.


Reviewed-by: Michael S. Tsirkin <mst@redhat.com>

> Changed in v2:
> 
>  - Remove hack that temporarily postponed automatic deletion
>    of machine types
>  - Fix docs version info for stable bugfix releases
> 
> Daniel P. Berrangé (5):
>   Revert "include/hw: temporarily disable deletion of versioned machine
>     types"
>   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             | 58 +++++++++++++++++++++------------
>  4 files changed, 89 insertions(+), 25 deletions(-)
> 
> -- 
> 2.49.0



      parent reply	other threads:[~2025-05-11 18:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-29 13:15 [PATCH v2 0/5] docs: automated info about machine deprecation/removal info Daniel P. Berrangé
2025-04-29 13:15 ` [PATCH v2 1/5] Revert "include/hw: temporarily disable deletion of versioned machine types" Daniel P. Berrangé
2025-04-29 14:30   ` Thomas Huth
2025-04-29 15:06     ` Daniel P. Berrangé
2025-04-29 13:15 ` [PATCH v2 2/5] include/hw/boards: cope with dev/rc versions in deprecation checks Daniel P. Berrangé
2025-04-29 15:26   ` Thomas Huth
2025-04-29 13:15 ` [PATCH v2 3/5] docs/about/deprecated: auto-generate a note for versioned machine types Daniel P. Berrangé
2025-04-29 15:29   ` Thomas Huth
2025-04-29 13:15 ` [PATCH v2 4/5] docs/about/removed-features: " Daniel P. Berrangé
2025-04-30 10:16   ` Thomas Huth
2025-04-29 13:15 ` [PATCH v2 5/5] include/hw/boards: add warning about changing deprecation logic Daniel P. Berrangé
2025-05-11 18:24 ` Michael S. Tsirkin [this message]

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=20250511142433-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=berrange@redhat.com \
    --cc=devel@lists.libvirt.org \
    --cc=eduardo@habkost.net \
    --cc=jsnow@redhat.com \
    --cc=marcel.apfelbaum@gmail.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).