qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-devel@nongnu.org, Peter Maydell <peter.maydell@linaro.org>,
	Stefan Hajnoczi <stefanha@redhat.com>,
	Markus Armbruster <armbru@redhat.com>,
	Eduardo Habkost <ehabkost@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v5 1/2 (for 2.10)] docs: document support lifetime for features
Date: Mon, 24 Jul 2017 16:26:24 +0200	[thread overview]
Message-ID: <d4f1f1c7-ca1f-904b-d23b-f9897b1ee29e@redhat.com> (raw)
In-Reply-To: <20170724141108.GA11443@redhat.com>

On 24/07/2017 16:11, Daniel P. Berrange wrote:
>>> +
>>> +The supported lifetime for versioned machine types is 12 releases,
>>> +which is equivalent to 4 years worth of previous QEMU releases.
>> I think there's still no consensus on this.
> 
> Indeed, which is exactly why I sent this patch - we need to come up
> with a sensible policy here, so we can stop repeating the same debate
> over & over & over each time some proposes a patch to kill off some
> random old machine type.
> 
> The 12 release / 4 year figure was a fairly arbitrary starting
> point to which I'd be hoping to see critical reviewer feedback
> on (with possible counterproposals) so we can try to get something
> documented, to put an end to the repeated debates in this area
> each time someone proposes a patch.

I agree.  At the moment, the status is "machine types never die".

We can change it, but I think that we should also make a decision on
whether removing machine types implies removing properties that only
exist for backwards-compatibility reasons.

4 year seems like a long time, but it can actually be pretty taxing for
RHEL.  I'm pretty sure that around RHEL 8.4 (some time between
2020-2022) we'll need a 1.5-ish machine type (2016).

Paolo

>>                                              The first two paragraphs
>> should be added to the documentation for -machine in qemu-options.hx,
>> since "-machine [type=]foo" is currently not documented at all.
> I'll happily send a patch for the docs for qemu-options.hx.

  reply	other threads:[~2017-07-24 14:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:08 [Qemu-devel] [PATCH v5 0/2 (for 2.10] Document deprecated features & support lifecycle Daniel P. Berrange
2017-07-19 10:08 ` [Qemu-devel] [PATCH v5 1/2 (for 2.10)] docs: document support lifetime for features Daniel P. Berrange
2017-07-19 11:56   ` Thomas Huth
2017-07-24 13:49     ` Paolo Bonzini
2017-07-24 14:11       ` Daniel P. Berrange
2017-07-24 14:26         ` Paolo Bonzini [this message]
2017-07-24 14:47           ` Daniel P. Berrange
2017-07-24 14:58             ` Paolo Bonzini
2017-07-19 10:08 ` [Qemu-devel] [PATCH v5 2/2 (for 2.10)] docs: document deprecated features in appendix Daniel P. Berrange
2017-07-19 11:51   ` Thomas Huth
2017-07-25  9:35   ` Thomas Huth
2017-07-25 11:21     ` Daniel P. Berrange
2017-07-24 13:45 ` [Qemu-devel] [PATCH v5 0/2 (for 2.10] Document deprecated features & support lifecycle Stefan Hajnoczi

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=d4f1f1c7-ca1f-904b-d23b-f9897b1ee29e@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=berrange@redhat.com \
    --cc=ehabkost@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    --cc=thuth@redhat.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).