All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures
Date: Thu, 16 Mar 2017 16:16:49 +0000	[thread overview]
Message-ID: <20170316161649.GZ15193@redhat.com> (raw)
In-Reply-To: <CAFEAcA9pqDoCWrPAJ+KVxLC_eRy-xRg36oYuARYg2YP8VpGpBg@mail.gmail.com>

On Thu, Mar 16, 2017 at 03:23:45PM +0000, Peter Maydell wrote:
> OK, here's a concrete proposal for deprecating/dropping out of
> date host OS and architecture support.
> 
> We'll put this in the ChangeLog 'Future incompatible changes'
> section:
> -----
> * Removal of support for untested host OS and architectures:
> 
> The QEMU Project intends to drop support in a future release for any
> host OS or architecture which we do not have access to a build and test
> machine for. This affects the following host OSes:
>  * Native CYGWIN building
>  * GNU/kFreeBSD
>  * FreeBSD
>  * DragonFly BSD
>  * NetBSD
>  * OpenBSD
>  * Solaris
>  * AIX
>  * Haiku
> and the following host CPU architectures:
>  * ia64
>  * sparc
> 
> Specifically, if we do not have a build and test system available
> to us by the time we release QEMU 2.10, we will remove support in the
> release that follows 2.10.

BTW, by "build & test system available", presumably you mean a system
that someone has committed to actively maintaining, not merely donation
of (or access to) hardware on which to install & run VMs ?

Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://entangle-photo.org       -o-    http://search.cpan.org/~danberr/ :|

  parent reply	other threads:[~2017-03-16 16:16 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 15:23 [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Peter Maydell
2017-03-16 15:46 ` Daniel P. Berrange
2017-03-16 15:55   ` Peter Maydell
2017-03-16 16:00     ` Daniel P. Berrange
2017-03-16 16:06       ` Peter Maydell
2017-03-16 16:12         ` Daniel P. Berrange
2017-03-17  9:09       ` Markus Armbruster
2017-03-16 16:52     ` Paolo Bonzini
2017-03-17  9:09       ` Thomas Huth
2017-03-17 10:12         ` Daniel P. Berrange
2017-03-17 10:15           ` Peter Maydell
2017-03-17 10:30             ` Thomas Huth
2017-03-17 10:48               ` Peter Maydell
2017-03-16 18:59     ` Dr. David Alan Gilbert
2017-03-17  9:58       ` Peter Maydell
2017-03-21 17:59   ` Eric Blake
2017-03-16 15:57 ` Gerd Hoffmann
2017-03-16 16:16 ` Daniel P. Berrange [this message]
2017-03-16 16:27   ` Peter Maydell
2017-03-16 18:01 ` Peter Maydell
2017-03-16 18:08   ` Daniel P. Berrange
2017-03-22 12:51   ` Alex Bennée
2017-03-22 13:09     ` Peter Maydell
2017-03-22 13:24       ` Thomas Huth
2017-03-23 10:33       ` Paolo Bonzini
2017-03-23 11:02         ` Peter Maydell
2017-03-24  1:28           ` Richard Henderson
2017-03-24 17:24             ` Peter Maydell
2017-03-22 19:07 ` [Qemu-devel] rawhide gcc failures [was: Proposal for deprecating unsupported host OSes & architecutures] Eric Blake
2017-03-22 19:39   ` Philippe Mathieu-Daudé
2017-03-27  6:36     ` Fam Zheng
2017-03-22 22:33   ` Peter Maydell
2017-03-23  9:25     ` Alex Bennée
2017-03-25 20:49 ` [Qemu-devel] Proposal for deprecating unsupported host OSes & architecutures Knut Omang
2017-03-25 21:15   ` Peter Maydell
2017-03-26  9:16     ` Knut Omang
2017-03-27 16:32       ` Peter Maydell
2017-03-28 18:34         ` Knut Omang

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=20170316161649.GZ15193@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.