From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel <qemu-devel@nongnu.org>, kvm-devel <kvm@vger.kernel.org>
Subject: [Qemu-devel] 1.0 Hard Freeze Logistics
Date: Mon, 31 Oct 2011 08:28:24 -0500 [thread overview]
Message-ID: <4EAEA278.7000901@us.ibm.com> (raw)
Hi,
Here are the logistics for the upcoming 1.0 hard freeze. All dates are
reflected in the wiki[1].
If you're a contributor and you've sent a series before the soft freeze
deadline, you've already done everything you need to do so sit back and enjoy
gorge yourself on Halloween candy.
If you're a submaintainer, the deadline for PULL requests for 1.0 hard freeze
will be EOD tomorrow (May 1st).
I encourage all submaintainers to spend today and tomorrow reviewing any
outstanding patches on the mailing list. I will do the same.
Once everything is processed, I'll update VERSION, and tag v1.0-rc0. I will not
upload a -rc0 tarball since this is basically a git snapshot. Unlike previous
releases, we will do this stable development in HEAD.
Our first release candidate will be tagged and released on November 7th (next
Tuesday). I'll do the release that Monday evening so that the -rc1 build is
available for out Test Day[2].
To make the Test Day more successful, please sign up to test a specific area on
the Test[3] wiki page.
We have a fairly long -rc cycle for this release so I expect submaintainers will
continue to maintain patches in their tree. I also think it would be good to
set up a -next staging tree but we can discuss that more in another thread.
[1] http://wiki.qemu.org/Planning/1.0
[2] http://mid.gmane.org/4EA94D53.3000707@redhat.com
[3] http://wiki.qemu.org/Planning/1.0/Testing
Regards,
Anthony Liguori
next reply other threads:[~2011-10-31 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-31 13:28 Anthony Liguori [this message]
2011-10-31 14:19 ` [Qemu-devel] 1.0 Hard Freeze Logistics Stefan Hajnoczi
2011-10-31 15:07 ` 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=4EAEA278.7000901@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=kvm@vger.kernel.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).