From: Christian Borntraeger <borntraeger@de.ibm.com>
To: Stefan Hajnoczi <stefanha@gmail.com>, qemu-devel <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [RFC] QEMU 2.10 release schedule
Date: Tue, 30 May 2017 13:21:01 +0200 [thread overview]
Message-ID: <eb4f47f8-ed16-f59b-4adc-1e4e94cadf7d@de.ibm.com> (raw)
In-Reply-To: <CAJSP0QVzoN=2rv_HUNf0oR_FQg=5xJ9UQbLqq0rj8OuYb8ZByw@mail.gmail.com>
On 05/30/2017 12:11 PM, Stefan Hajnoczi wrote:
> Here is a first stab at the next release schedule:
>
> Beginning of development phase: 2017-04-20
> Soft feature freeze: 2017-07-18
> -rc0: 2017-07-25
> -rc1: 2017-08-01
> -rc2: 2017-08-08
> -rc3: 2017-08-15
> -rc4: 2017-08-22
>
- rc4/release or really only rc4?
> Thoughts?
> Stefan
>
next prev parent reply other threads:[~2017-05-30 11:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-30 10:11 [Qemu-devel] [RFC] QEMU 2.10 release schedule Stefan Hajnoczi
2017-05-30 11:07 ` Paolo Bonzini
2017-05-30 11:21 ` Christian Borntraeger [this message]
2017-05-31 13:06 ` Stefan Hajnoczi
2017-06-07 18:24 ` Marc-André Lureau
2017-06-08 10:13 ` Stefan Hajnoczi
2017-05-31 14:25 ` Peter Maydell
2017-05-31 15:18 ` Alex Bennée
2017-06-08 10:14 ` Stefan Hajnoczi
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=eb4f47f8-ed16-f59b-4adc-1e4e94cadf7d@de.ibm.com \
--to=borntraeger@de.ibm.com \
--cc=peter.maydell@linaro.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).