From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel@nongnu.org, Yanan Wang <wangyanan55@huawei.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
devel@lists.libvirt.org,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Zhao Liu <zhao1.liu@intel.com>,
Eduardo Habkost <eduardo@habkost.net>,
Peter Maydell <peter.maydell@linaro.org>,
John Snow <jsnow@redhat.com>
Subject: Re: [PATCH v3 2/5] include/hw/boards: cope with dev/rc versions in deprecation checks
Date: Thu, 8 May 2025 11:23:12 +0100 [thread overview]
Message-ID: <aByGENuj1O-SJ_xG@redhat.com> (raw)
In-Reply-To: <3b92958c-c99f-4c9c-96b6-c5fbaaec06fc@linaro.org>
On Thu, May 08, 2025 at 12:21:20PM +0200, Philippe Mathieu-Daudé wrote:
> On 8/5/25 10:53, Daniel P. Berrangé wrote:
> > On Thu, May 08, 2025 at 09:45:50AM +0200, Thomas Huth wrote:
> > > On 06/05/2025 18.00, Daniel P. Berrangé wrote:
> > > > When VERSION is set to a development snapshot (micro >= 50), or a release
> > > > candidate (micro >= 90) we have an off-by-1 in determining deprecation
> > > > and deletion thresholds for versioned machine types. In such cases we need
> > > > to use the next major/minor version in threshold checks.
> > > >
> > > > This adapts the deprecation macros to do "next version" prediction when
> > > > seeing a dev/rc version number.
> > > >
> > > > This ensures users of release candidates get an accurate view of machines
> > > > that will be deprecated/deleted in the final release.
> > > >
> > > > This requires hardcoding our current release policy of 3 releases per
> > > > year, with a major bump at the start of each year, and that dev/rc
> > > > versions have micro >= 50.
> > > >
> > > > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > > > ---
> > > > include/hw/boards.h | 33 ++++++++++++++++++++++++++++++++-
> > > > 1 file changed, 32 insertions(+), 1 deletion(-)
> > >
> > > FYI, this causes a failure in the CI now:
> > >
> > > https://gitlab.com/thuth/qemu/-/jobs/9965651507#L163
>
> Ah, just noticed the same error msg:
>
> qemu-system-x86_64: unsupported machine type: "pc-q35-4.1"
>
> > >
> > > Looks like we have to remove the related subtest now?
>
> Hmmm shouldn't we merge this series on top of up-to-4.1 machines
> removal?
There's no dependency on that series in general, just removal of the
test case. We need to remove that test case regardless, because our
machines will automatically remove registration of the machine type,
regardless of whether the code is deleted.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2025-05-08 10:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-06 16:00 [PATCH v3 0/5] docs: automated info about machine deprecation/removal info Daniel P. Berrangé
2025-05-06 16:00 ` [PATCH v3 1/5] Revert "include/hw: temporarily disable deletion of versioned machine types" Daniel P. Berrangé
2025-05-06 16:00 ` [PATCH v3 2/5] include/hw/boards: cope with dev/rc versions in deprecation checks Daniel P. Berrangé
2025-05-08 7:45 ` Thomas Huth
2025-05-08 8:53 ` Daniel P. Berrangé
2025-05-08 10:21 ` Philippe Mathieu-Daudé
2025-05-08 10:23 ` Daniel P. Berrangé [this message]
2025-05-08 11:16 ` Philippe Mathieu-Daudé
2025-05-06 16:00 ` [PATCH v3 3/5] docs/about/deprecated: auto-generate a note for versioned machine types Daniel P. Berrangé
2025-05-06 16:00 ` [PATCH v3 4/5] docs/about/removed-features: " Daniel P. Berrangé
2025-05-06 16:00 ` [PATCH v3 5/5] include/hw/boards: add warning about changing deprecation logic Daniel P. Berrangé
2025-05-06 17:53 ` [PATCH v3 0/5] docs: automated info about machine deprecation/removal info Thomas Huth
2025-05-08 11:17 ` Philippe Mathieu-Daudé
2025-05-09 16:55 ` Michael S. Tsirkin
2025-05-11 13:20 ` Michael S. Tsirkin
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=aByGENuj1O-SJ_xG@redhat.com \
--to=berrange@redhat.com \
--cc=devel@lists.libvirt.org \
--cc=eduardo@habkost.net \
--cc=jsnow@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.