From: "Daniel P. Berrange" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
qemu-devel@nongnu.org, patches@linaro.org,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [Qemu-devel] [PATCH] configure: Drop AIX host support
Date: Tue, 5 Sep 2017 09:04:18 +0100 [thread overview]
Message-ID: <20170905080418.GA311@redhat.com> (raw)
In-Reply-To: <d91a4033-a76a-9adc-aaa0-ded8468a337b@redhat.com>
On Mon, Sep 04, 2017 at 08:09:17PM +0200, Thomas Huth wrote:
> On 04.09.2017 19:19, Peter Maydell wrote:
> > Nobody has mentioned AIX host support on the mailing list for years,
> > and we have no test systems for it so it is most likely broken.
> > We've advertised in configure for two releases now that we plan
> > to drop support for this host OS, and have had no complaints.
>
> We just added this some weeks ago to our qemu-doc.texi:
>
> "Prior to the 2.10.0 release there was no official policy on how long
> features would be deprecated prior to their removal, nor any documented
> list of which features were deprecated. Thus any features deprecated
> prior to 2.10.0 will be treated as if they were first deprecated in the
> 2.10.0 release."
>
> Should we maybe wait two more releases (for version 3.0 ;-)) 'till we
> remove it?
The deprecation policy is for features which currently work and which we
expect to have actual users. Neither is the case with AIX support, so I
don't see any reason to keep it longer.
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:[~2017-09-05 8:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-04 17:19 [Qemu-devel] [PATCH] configure: Drop AIX host support Peter Maydell
2017-09-04 17:59 ` Philippe Mathieu-Daudé
2017-09-04 18:09 ` Thomas Huth
2017-09-04 18:20 ` Peter Maydell
2017-09-05 7:16 ` Markus Armbruster
2017-09-05 7:36 ` Thomas Huth
2017-09-05 15:28 ` Peter Maydell
2017-09-05 8:04 ` Daniel P. Berrange [this message]
2017-09-05 8:15 ` Thomas Huth
2017-09-04 18:57 ` Laurent Vivier
2017-09-04 20:50 ` Kamil Rytarowski
2017-09-05 8:01 ` Greg Kurz
2017-09-05 9:26 ` Stefan Hajnoczi
2017-09-08 9:21 ` Peter Maydell
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=20170905080418.GA311@redhat.com \
--to=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=laurent@vivier.eu \
--cc=patches@linaro.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--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).