From: zhanghailiang <zhang.zhanghailiang@huawei.com>
To: Peter Maydell <peter.maydell@linaro.org>,
QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] 2.3 schedule (HARDFREEZE 2014-03-17)
Date: Thu, 12 Mar 2015 09:05:37 +0800 [thread overview]
Message-ID: <5500E661.9060403@huawei.com> (raw)
In-Reply-To: <CAFEAcA8FVg8GQ618fhti1aGM4teayeQCUJstqaLDm-SR3VL=Uw@mail.gmail.com>
On 2015/3/11 22:25, Peter Maydell wrote:
> Hi; since I was on holiday the 2.3 schedule got a bit lost/delayed.
> Discussion on IRC suggests:
>
> 2014-03-17: hardfreeze and rc0
> 2014-03-24: rc1
> 2014-03-31: rc2
> 2014-04-07: rc3
> 2014-04-14: final release
>
s/2014/2015
;) wiki is right.
> (I've updated http://wiki.qemu.org/Planning/2.3.)
>
> I plan to apply all the outstanding pull requests before the 17th.
> We might need to delay rc0 tagging if there are still any particularly
> nasty known issues to be squashed.
>
> Remember that we are in softfreeze so don't be too enthusiastic
> about pushing new stuff before the 17th :-)
>
> thanks
> -- PMM
>
>
>
prev parent reply other threads:[~2015-03-12 1:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-11 14:25 [Qemu-devel] 2.3 schedule (HARDFREEZE 2014-03-17) Peter Maydell
2015-03-12 1:05 ` zhanghailiang [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=5500E661.9060403@huawei.com \
--to=zhang.zhanghailiang@huawei.com \
--cc=peter.maydell@linaro.org \
--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).