From: Markus Armbruster <armbru@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Mark McLoughlin <markmc@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel\@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 03:10:49 +0200 [thread overview]
Message-ID: <87eisp1gx2.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <4A55F150.3020803@codemonkey.ws> (Anthony Liguori's message of "Thu\, 09 Jul 2009 08\:32\:00 -0500")
Anthony Liguori <anthony@codemonkey.ws> writes:
> Mark McLoughlin wrote:
>> Hi Anthony,
>>
>> On Mon, 2009-06-22 at 18:57 -0500, Anthony Liguori wrote:
>>
>>> Hi,
>>>
>>> It's getting to be about the time to start thinking about the
>>> 0.11.0 release. 0.10.0 was released on March 2nd so following with
>>> the 6 month release cycle, that would put 0.11.0 at September 2nd.
>>>
>>> Based on the experiences with the stable releases, here's what I'd
>>> recommend:
>>>
>>> o On July 15th, fork master -> stable-0.11
>>>
>>
>> Are you still planning on creating the 0.11 branch next week?
>>
>
> That's the plan although I need to make sure that all outstanding
> patches have been given adequate review before hand. I want to give
> any patch that has been posted so far a reasonable chance to make it
> into 0.11. If I can get through the backlog today, then we'll stay on
> schedule. Either way, there will be plenty of warning on the ML and
> opportunity for people to make suggestions.
>
> Regards,
>
> Anthony Liguori
Any hope that -device can make the cut?
WARNING: multiple messages have this Message-ID (diff)
From: Markus Armbruster <armbru@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: Mark McLoughlin <markmc@redhat.com>,
Anthony Liguori <aliguori@us.ibm.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Planning for the 0.11.0 release
Date: Fri, 10 Jul 2009 03:10:49 +0200 [thread overview]
Message-ID: <87eisp1gx2.fsf@pike.pond.sub.org> (raw)
In-Reply-To: <4A55F150.3020803@codemonkey.ws> (Anthony Liguori's message of "Thu\, 09 Jul 2009 08\:32\:00 -0500")
Anthony Liguori <anthony@codemonkey.ws> writes:
> Mark McLoughlin wrote:
>> Hi Anthony,
>>
>> On Mon, 2009-06-22 at 18:57 -0500, Anthony Liguori wrote:
>>
>>> Hi,
>>>
>>> It's getting to be about the time to start thinking about the
>>> 0.11.0 release. 0.10.0 was released on March 2nd so following with
>>> the 6 month release cycle, that would put 0.11.0 at September 2nd.
>>>
>>> Based on the experiences with the stable releases, here's what I'd
>>> recommend:
>>>
>>> o On July 15th, fork master -> stable-0.11
>>>
>>
>> Are you still planning on creating the 0.11 branch next week?
>>
>
> That's the plan although I need to make sure that all outstanding
> patches have been given adequate review before hand. I want to give
> any patch that has been posted so far a reasonable chance to make it
> into 0.11. If I can get through the backlog today, then we'll stay on
> schedule. Either way, there will be plenty of warning on the ML and
> opportunity for people to make suggestions.
>
> Regards,
>
> Anthony Liguori
Any hope that -device can make the cut?
next prev parent reply other threads:[~2009-07-10 1:11 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-22 23:57 Planning for the 0.11.0 release Anthony Liguori
2009-06-22 23:57 ` [Qemu-devel] " Anthony Liguori
2009-06-23 12:12 ` Avi Kivity
2009-06-23 15:09 ` Blue Swirl
2009-06-23 15:47 ` Anthony Liguori
2009-06-23 15:49 ` Avi Kivity
2009-07-09 8:27 ` Mark McLoughlin
2009-07-09 13:32 ` Anthony Liguori
2009-07-10 1:10 ` Markus Armbruster [this message]
2009-07-10 1:10 ` Markus Armbruster
2009-07-10 13:53 ` Anthony Liguori
2009-07-10 15:04 ` Jan Kiszka
2009-07-10 15:04 ` Jan Kiszka
2009-07-10 15:49 ` Anthony Liguori
2009-07-10 15:49 ` Anthony Liguori
2009-07-10 16:23 ` Jan Kiszka
2009-07-10 16:23 ` Jan Kiszka
2009-07-10 16:33 ` Anthony Liguori
2009-07-10 16:33 ` Anthony Liguori
2009-07-10 16:52 ` Jan Kiszka
2009-07-10 16:52 ` Jan Kiszka
2009-07-10 17:03 ` Anthony Liguori
2009-07-10 17:03 ` Anthony Liguori
2009-07-10 17:15 ` Jan Kiszka
2009-07-10 17:15 ` Jan Kiszka
2009-07-10 17:40 ` Paul Brook
2009-07-10 17:40 ` Paul Brook
2009-07-10 17:58 ` Anthony Liguori
2009-07-10 17:58 ` Anthony Liguori
2009-07-10 18:02 ` Jan Kiszka
2009-07-10 18:02 ` Jan Kiszka
2009-07-10 18:22 ` Paul Brook
2009-07-10 18:22 ` Paul Brook
2009-07-10 16:55 ` Kevin Wolf
2009-07-10 16:59 ` Anthony Liguori
2009-07-10 17:10 ` Kevin Wolf
2009-07-10 17:31 ` Anthony Liguori
2009-07-10 17:10 ` Christoph Hellwig
2009-07-10 17:12 ` Kevin Wolf
2009-07-10 17:12 ` Kevin Wolf
2009-07-10 18:26 ` Christoph Hellwig
2009-07-10 18:26 ` Christoph Hellwig
2009-07-10 17:29 ` Anthony Liguori
2009-07-10 18:13 ` Christoph Hellwig
2009-07-10 18:13 ` Christoph Hellwig
2009-07-10 18:29 ` Anthony Liguori
2009-07-10 17:06 ` Anthony Liguori
2009-07-12 8:31 ` 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=87eisp1gx2.fsf@pike.pond.sub.org \
--to=armbru@redhat.com \
--cc=aliguori@us.ibm.com \
--cc=anthony@codemonkey.ws \
--cc=kvm@vger.kernel.org \
--cc=markmc@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 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.