From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [RFC] QEMU 1.2.0 Release Schedule
Date: Sat, 02 Jun 2012 17:52:01 +0800 [thread overview]
Message-ID: <4FC9E241.5020305@codemonkey.ws> (raw)
Summary: GA on September 1st, shorten feature freeze to 2.5 weeks.
We've discussed a lot in the past moving to a quarterly release cycle. More
frequent releases will allow distributions to more easily ship newer versions of
QEMU.
Here's the schedule (also available on the wiki):
http://wiki.qemu.org/Planning/1.2
| 2011-06-01
| Beginning of 1.2 development phase
|-
| 2012-07-01
| [[Planning/Sprint|Sprint]] 1
|-
| 2012-08-01
| [[Planning/SoftFeatureFreeze|Soft feature freeze]]. Major features should
have initial code committed by this date.
|-
| 2012-08-15
| [[Planning/HardFeatureFreeze|Hard feature freeze]]. Tag v1.2.0-rc0, only bug
fixes committed after this point
|-
| 2012-08-22
| Tag v1.2.0-rc1
|-
| 2012-08-29
| Tag v1.2.0-rc2
|-
| 2012-09-01
| Tag v1.2.0
Regards,
Anthony Liguori
next reply other threads:[~2012-06-02 9:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 9:52 Anthony Liguori [this message]
2012-06-02 20:16 ` [Qemu-devel] [RFC] QEMU 1.2.0 Release Schedule Blue Swirl
2012-06-02 22:07 ` Anthony Liguori
2012-06-02 22:11 ` Peter Maydell
2012-06-02 22:26 ` Anthony Liguori
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=4FC9E241.5020305@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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.