From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: Michael Tokarev <mjt@tls.msk.ru>
Subject: [Qemu-devel] [RFC] Policy for supported hosts/platforms
Date: Wed, 05 Jun 2013 09:04:00 -0500 [thread overview]
Message-ID: <87vc5s4ptb.fsf@codemonkey.ws> (raw)
Hi,
Below is the coverage we currently have in buildbot. It's not terribly
complete but I suspect it does reflect what people are actually testing
and care about.
In terms of policy, we should consider buildbot coverage as a
requirement for a platform/architecture to be fully supported. Fully
supported means (1) that code will be rejected/reverted if it breaks one
of these platforms (2) breaking these platforms will be a release
blocker.
Anything that isn't fully supported is best effort only. Note that are
some things missing from buildbot today (like an ARM host) that there is
strong interest in having as a fully supported platform.
Host Arch
---------
s390 (offline since May 1st)
PPC
Sparc (offline since 2011)
x86_64
i386
Host OS
-------
Solaris 11 (offline since 2011)
Debian 6.0
RHEL 6.1
RHEL 5.x
Fedora 16
OpenBSD (current)
OpenBSD 4.9
Mingw32
MacOS X
Regards,
Anthony Liguori
next reply other threads:[~2013-06-05 14:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 14:04 Anthony Liguori [this message]
2013-06-05 15:22 ` [Qemu-devel] [RFC] Policy for supported hosts/platforms Ed Maste
2013-06-05 18:16 ` Brad Smith
2013-06-20 13:58 ` Ed Maste
2013-07-01 11:47 ` Stefan Hajnoczi
2013-07-01 12:10 ` Ed Maste
2013-07-02 7:31 ` Stefan Hajnoczi
2013-07-02 7:35 ` Christian Berendt
2013-07-03 8:57 ` Stefan Hajnoczi
2013-07-08 15:15 ` Ed Maste
2013-07-18 0:07 ` Ed Maste
2013-09-09 18:15 ` Ed Maste
2013-09-10 7:44 ` Stefan Hajnoczi
2013-09-18 12:57 ` Ed Maste
2013-09-18 13:05 ` Christian Berendt
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=87vc5s4ptb.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=mjt@tls.msk.ru \
--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 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).