From: aliguori@us.ibm.com
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] 1.2 Hard Freeze approaching
Date: Tue, 07 Aug 2012 09:51:45 -0500 [thread overview]
Message-ID: <87r4riah6m.fsf@codemonkey.ws> (raw)
Hi,
I just wanted to send out a friendly reminder that the 1.2 hard freeze
is quickly approaching.
If you have any series that you're targetting for 1.2, now is the time
to get the final versions on the mailing list.
If you aren't already, it's probably a good time to start marking patch
series as for-1.2 to explicitly alert maintainers of your intention.
For anyone submitting a pull request, please make sure to send a PULL
request by EOD Wednesday, August 15th so I can prepare an -rc0 release.
Preferrably, you should send the pull requests by EOD Tuesday.
We have a very short -rc cycle for this release so I'm planning on being
very strict about the hard freeze so please make every effort to get
changes in before the 15th.
http://wiki.qemu.org/Planning/1.2
Regards,
Anthony Liguori
reply other threads:[~2012-08-07 14:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87r4riah6m.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--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).