From: Brad Smith <brad@comstyle.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Michael Tokarev <mjt@tls.msk.ru>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC] Policy for supported hosts/platforms
Date: Wed, 05 Jun 2013 14:16:07 -0400 [thread overview]
Message-ID: <51AF8067.3020506@comstyle.com> (raw)
In-Reply-To: <87vc5s4ptb.fsf@codemonkey.ws>
On 05/06/13 10:04 AM, Anthony Liguori wrote:
>
> 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 OS
> -------
>
> Solaris 11 (offline since 2011)
IMO having an active Solaris buildslave is fairly important.
> OpenBSD 4.9
It is labelled as 4.9 but it was upgraded to 5.2 awhile ago and I had
asked Gerd if he could upgrade it to 5.3 when he has the time.
In addition to the FreeBSD buildslaves mentioned by Ed it would be nice
to have a NetBSD 6.1 buildslave.
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
next prev parent reply other threads:[~2013-06-05 18:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 14:04 [Qemu-devel] [RFC] Policy for supported hosts/platforms Anthony Liguori
2013-06-05 15:22 ` Ed Maste
2013-06-05 18:16 ` Brad Smith [this message]
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=51AF8067.3020506@comstyle.com \
--to=brad@comstyle.com \
--cc=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 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.