From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Markus Armbruster <armbru@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
Eduardo Habkost <ehabkost@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, kraxel@redhat.com,
Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] hw/i386: Deprecate the machines pc-0.10 to pc-0.15
Date: Wed, 10 May 2017 20:04:59 +0100 [thread overview]
Message-ID: <20170510190459.GD3941@work-vm> (raw)
In-Reply-To: <87tw4su3iw.fsf@dusky.pond.sub.org>
* Markus Armbruster (armbru@redhat.com) wrote:
> Thomas Huth <thuth@redhat.com> writes:
>
> > On 10.05.2017 11:08, Daniel P. Berrange wrote:
> >> On Wed, May 10, 2017 at 08:48:53AM +0200, Thomas Huth wrote:
> [...]
> >> Also unless we're going to get more serious about automated testing to
> >> validate machine type compatibility between *all* previously releases,
> >> I think that 6 years / 18 releases is too long a time to have any
> >> confidence in migration compatibility between versions.
>
> Seconded.
>
> > Distro vendors often offer 5 - 10 years support for certain versions of
> > their Linux distros, so I think we should at least support 5 years, too.
>
> Non sequitur.
>
> Distro vendors put in serious work to keep versions working for 5 - 10
> years. We can't, and we don't. All we do is try not to break things,
> which is nice, and helps the distro vendors some, but a far cry from
> anything I'd dare call "support".
>
> Perhaps an argument could be made that us keeping to try for at least 5
> years would help distro vendors enough to be worthwhile. Maybe, but
> color me skeptic.
Since I'm often the one having to fix the breakages when we find they've
diverged, I would prefer us to try to keep them working upstream.
Every time something slips through upstream it's more work for me.
Dave
> >> IOW, I think you should be more aggressive in culling old machine types
> >> that this patch is...
> >
> > Actually, I like the idea of using the major release versions for
> > defining the set of removal - hoping that we will do a v3.0 next year
> > which then would support the previous two major release versions 1.x and
> > 2.x, but drops support for the 0.xx versions completely ...
>
> I wouldn't put *that* much weight into our past version numbers. If I
> remember correctly, there was no more to 1.0 than a feeling of "this 0.x
> thing is getting ridiculous".
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-05-10 19:05 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 6:48 [Qemu-devel] [PATCH] hw/i386: Deprecate the machines pc-0.10 to pc-0.15 Thomas Huth
2017-05-10 9:08 ` Daniel P. Berrange
2017-05-10 10:05 ` Thomas Huth
2017-05-10 10:31 ` Daniel P. Berrange
2017-05-10 14:47 ` Thomas Huth
2017-05-10 16:15 ` Paolo Bonzini
2017-05-11 7:06 ` Markus Armbruster
2017-05-11 7:21 ` Thomas Huth
2017-05-11 9:30 ` Daniel P. Berrange
2017-05-11 15:10 ` Markus Armbruster
2017-05-12 6:55 ` Thomas Huth
2017-05-10 15:37 ` Markus Armbruster
2017-05-10 15:40 ` Paolo Bonzini
2017-05-10 19:04 ` Dr. David Alan Gilbert [this message]
2017-05-11 7:20 ` Markus Armbruster
2017-05-10 14:51 ` Dr. David Alan Gilbert
2017-05-10 15:04 ` Daniel P. Berrange
2017-05-10 15:14 ` Dr. David Alan Gilbert
2017-05-11 7:26 ` Markus Armbruster
2017-05-10 15:05 ` Paolo Bonzini
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=20170510190459.GD3941@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kraxel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--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).