From: Kevin Wolf <kwolf@redhat.com>
To: Aurelien Jarno <aurelien@aurel32.net>
Cc: Anthony Liguori <aliguori@linux.vnet.ibm.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] 0.14.0 release schedule
Date: Tue, 25 Jan 2011 16:55:30 +0100 [thread overview]
Message-ID: <4D3EF272.7060204@redhat.com> (raw)
In-Reply-To: <4D3EF0E2.9030601@aurel32.net>
Am 25.01.2011 16:48, schrieb Aurelien Jarno:
> Anthony Liguori a écrit :
>> Here's my proposal:
>>
>> Stable branch - 2/1
>>
>> 1 or 2 -rcs in between
>>
>> Stable release - 2/15
>>
>
> It looks fine to me. The important is more probably to have a schedule
> than the schedule itself.
Right, I agree. The schedule is fine with me, too.
Kevin
prev parent reply other threads:[~2011-01-25 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 15:10 [Qemu-devel] 0.14.0 release schedule Anthony Liguori
2011-01-25 15:48 ` Aurelien Jarno
2011-01-25 15:55 ` Kevin Wolf [this message]
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=4D3EF272.7060204@redhat.com \
--to=kwolf@redhat.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=aurelien@aurel32.net \
--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.