From: Anthony Liguori <anthony@codemonkey.ws>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Chris Wright <chrisw@redhat.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
Luiz Capitulino <lcapitulino@redhat.com>
Subject: Re: [Qemu-devel] Re: KVM call agenda for Jan 25
Date: Tue, 25 Jan 2011 08:27:44 -0600 [thread overview]
Message-ID: <4D3EDDE0.9000000@codemonkey.ws> (raw)
In-Reply-To: <4D3EDA27.2060408@aurel32.net>
On 01/25/2011 08:11 AM, Aurelien Jarno wrote:
> Luiz Capitulino a écrit :
>
>> On Mon, 24 Jan 2011 16:06:34 -0600
>> Anthony Liguori<anthony@codemonkey.ws> wrote:
>>
>>
>>> On 01/24/2011 07:25 AM, Chris Wright wrote:
>>>
>>>> Please send in any agenda items you are interested in covering.
>>>>
>>>>
>>> - coroutines for the block layer
>>> - glib everywhere
>>>
>> - Let's start planning our next release in advance, here's a simple example:
>>
>> http://wiki.qemu.org/Planning/0.15-example
>>
>>
> What about planning the 0.14 release first? From what I see on the
> mailing list, we are more in a development phase than in a bug fix phase
> before a release.
>
Yeah, lesson learned is releasing before a holiday is probably a bad idea.
What would be a reasonable window to get us in bug fixing mode to do a
release? How would a 2/1 stable-0.14 branch sound?
Regards,
Anthony Liguori
next prev parent reply other threads:[~2011-01-25 14:27 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-24 13:25 [Qemu-devel] KVM call agenda for Jan 25 Chris Wright
2011-01-24 22:06 ` [Qemu-devel] " Anthony Liguori
2011-01-25 13:57 ` Luiz Capitulino
2011-01-25 14:02 ` Luiz Capitulino
2011-01-25 14:13 ` Stefan Hajnoczi
2011-01-29 10:50 ` Dushyant Bansal
2011-01-29 13:16 ` Stefan Hajnoczi
2011-02-25 17:42 ` Dushyant Bansal
2011-02-26 14:05 ` Stefan Hajnoczi
2011-02-26 21:50 ` Dushyant Bansal
2011-02-27 10:49 ` Stefan Hajnoczi
2011-02-28 7:36 ` Markus Armbruster
2011-02-28 20:41 ` Dushyant Bansal
2011-03-01 9:40 ` Stefan Hajnoczi
2011-03-14 15:13 ` Dushyant Bansal
2011-03-15 10:27 ` Kevin Wolf
2011-03-16 14:17 ` Dushyant Bansal
2011-03-16 17:47 ` Stefan Hajnoczi
2011-03-17 10:07 ` Kevin Wolf
2011-03-26 21:56 ` Dushyant Bansal
2011-03-28 10:26 ` Kevin Wolf
2011-01-25 14:11 ` Aurelien Jarno
2011-01-25 14:27 ` Anthony Liguori [this message]
2011-01-25 14:42 ` Kevin Wolf
2011-01-25 15:29 ` Aurelien Jarno
2011-01-25 14:26 ` Avi Kivity
2011-01-25 14:35 ` Stefan Hajnoczi
2011-01-26 9:58 ` 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=4D3EDDE0.9000000@codemonkey.ws \
--to=anthony@codemonkey.ws \
--cc=aurelien@aurel32.net \
--cc=chrisw@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--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).