On Mon, Jun 10, 2024 at 9:39 AM Markus Armbruster wrote:
> Daniel P. Berrangé writes:
>
> > On Thu, Jun 06, 2024 at 01:22:14PM -0400, John Snow wrote:
> >> On Thu, Jun 6, 2024 at 6:25 AM Victor Toso
> wrote:
> >> > On Wed, Jun 05, 2024 at 11:47:53AM GMT, John Snow wrote:
> >> Importantly, old v
Daniel P. Berrangé writes:
> On Thu, Jun 06, 2024 at 01:22:14PM -0400, John Snow wrote:
>> On Thu, Jun 6, 2024 at 6:25 AM Victor Toso wrote:
>> > On Wed, Jun 05, 2024 at 11:47:53AM GMT, John Snow wrote:
>> Importantly, old versions of the schema aren't contained *entirely* within
>> the schema.
On Thu, Jun 06, 2024 at 01:22:14PM -0400, John Snow wrote:
> On Thu, Jun 6, 2024 at 6:25 AM Victor Toso wrote:
> > On Wed, Jun 05, 2024 at 11:47:53AM GMT, John Snow wrote:
> Importantly, old versions of the schema aren't contained *entirely* within
> the schema. Here's a timeline:
>
> v0.12.0: QM
Adding upstream because I think there's little reason to keep this
discussion off-list.
The context of this mailing thread is that we are discussing how we might
want to store and record historical QMP API interface information such that
we can programmatically answer questions like "when was X co
