From: Lucas Meneghel Rodrigues <lmr@redhat.com>
To: Stefan Hajnoczi <stefanha@gmail.com>
Cc: "Justin M. Forbes" <jmforbes@linuxtx.org>,
qemu-devel <qemu-devel@nongnu.org>, Avi Kivity <avi@redhat.com>
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 0.15.0-rc1 Release
Date: Thu, 04 Aug 2011 12:20:42 -0300 [thread overview]
Message-ID: <4E3AB8CA.3000808@redhat.com> (raw)
In-Reply-To: <CAJSP0QV8esgQGZyGwb=sc8LqT9E155sX9G2cZxRyGnxQ6TuL+g@mail.gmail.com>
On 08/04/2011 12:17 PM, Stefan Hajnoczi wrote:
> On Sat, Jul 30, 2011 at 1:39 AM, Anthony Liguori<anthony@codemonkey.ws> wrote:
>> On behalf of the entire QEMU team, I'm please to announce the release of
>> QEMU 0.15.0-rc1. This is the second release candidate for the 0.15.0
>> release.
>>
>> There are numerous ways you can help participate in the 0.15.0 release.
>> There is a testing coordination wiki page located at:
>>
>> http://wiki.qemu.org/Planning/0.15/Testing
>
> Hi Lucas,
> Is QEMU 0.15.0-rc1 being run through KVM-Autotest?
We always test git master HEAD, so, no. I can look at testing specific
tags or branches to help with that. The release branch/tag testing was
just not on my radar so far.
So, I didn't take a closer look, but I assume the release work is made
through a release branch or something?
> Stefan
next prev parent reply other threads:[~2011-08-04 15:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 0:39 [Qemu-devel] [ANNOUNCE] QEMU 0.15.0-rc1 Release Anthony Liguori
2011-07-31 8:06 ` Avi Kivity
2011-07-31 20:39 ` Anthony Liguori
2011-07-31 16:31 ` Avi Kivity
2011-07-31 20:57 ` Anthony Liguori
2011-08-04 15:17 ` Stefan Hajnoczi
2011-08-04 15:20 ` Lucas Meneghel Rodrigues [this message]
2011-08-05 6:04 ` Stefan Hajnoczi
2011-08-04 15:25 ` Avi Kivity
2011-08-04 15:38 ` Anthony Liguori
2011-08-04 15:47 ` Avi Kivity
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=4E3AB8CA.3000808@redhat.com \
--to=lmr@redhat.com \
--cc=avi@redhat.com \
--cc=jmforbes@linuxtx.org \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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).