On 3/12/2026 2:25 AM, Eric Auger wrote:
On 3/12/26 10:20 AM, Markus Armbruster wrote:
Eric Auger<[email protected]> writes:
On 3/12/26 9:39 AM, Markus Armbruster wrote:
[...]
We promise to follow a certain process when changing external
interfaces: docs/about/deprecated.rst.
This is why I inquired about external access. No external access, no
compatibility worries.
I specifically asked about JSON, because going from bool to OnOffAuto is
mostly compatible in key=value syntax: values "on" and "off" keep
working.
Mostly compatible, because qapi_bool_parse() also recognizes "yes",
"true", "y", "no", "false", and "n" for convenience, and these stop
working. We have a knack for inventing convenience features that later
bite us.
JSON breaks entirely, of course: all values stop working.
Even with external access, compatibility worries start only after we
shipped the interface in a release. Did we?
those options were introduced in qemu 11.0. Fixing them in -rc is still
an option but it is a very tight schedule
If it turns out to be too tight, rever them or declare them
experimental? Then you can revise them without process hassle in the
next release.
Maybe Nathan, in a first step, you could just respin and convert the
options to the auto form, keeping the current default value and not
implementing the auto mode yet.
+ the ATS check fix? Shameer, Nathan, would that be sensible within the
qemu 11.0 -rc timeframe.
Yes, we will respin with just the auto form conversion and include the
ATS check fix.
Thanks,
Nathan
