From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away)
Date: Wed, 21 Sep 2011 19:34:18 -0500 [thread overview]
Message-ID: <4E7A828A.3030404@codemonkey.ws> (raw)
Consider this a friendly reminder that we're only three weeks away from the soft
feature freeze for 1.0. I've written a wiki page about my expectations for the
soft feature freeze. It's inlined here for easier commenting.
== What is the soft feature freeze? ==
The soft feature freeze is the beginning of the stabilization phase of QEMU's
development process. By the date of the soft feature freeze, any major feature
should have some code posted to the qemu-devel mailing list if it's targeting a
given release.
== What should I do by the soft feature freeze? ==
For any major feature that you're targeting to the next release, you should:
# Make sure that you've posted a patch series to qemu-devel
# Write a Feature page on the qemu.org wiki describing the feature and the
motivation
# On the release planning wiki page, link to your feature wiki page.
== Will my patches be rejected if I don't post before the soft feature freeze? ==
That's ultimately up to the subsystem maintainer. It's a value call based on
the relative importance of the feature verses the disruptiveness of the feature.
It's always best to avoid this problem in the first place and release early,
release often[http://en.wikipedia.org/wiki/Release_early,_release_often].
next reply other threads:[~2011-09-22 0:34 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 0:34 Anthony Liguori [this message]
2011-09-24 8:05 ` [Qemu-devel] [FYI] Soft feature freeze for 1.0 is 10/15 (three weeks away) Blue Swirl
2011-09-25 14:10 ` Avi Kivity
2011-09-25 16:36 ` Blue Swirl
2011-09-25 16:48 ` Avi Kivity
2011-09-25 17:31 ` Blue Swirl
2011-09-26 10:08 ` Avi Kivity
2011-09-26 10:10 ` Avi Kivity
2011-09-26 17:15 ` Blue Swirl
2011-09-26 17:18 ` Avi Kivity
2011-09-26 17:20 ` Blue Swirl
2011-09-26 17:24 ` Avi Kivity
2011-09-26 18:07 ` Blue Swirl
2011-09-27 8:33 ` Avi Kivity
2011-09-27 8:57 ` Avi Kivity
2011-09-27 16:39 ` Blue Swirl
2011-09-27 16:44 ` Avi Kivity
2011-09-27 19:19 ` Blue Swirl
2011-09-28 21:21 ` Alexander Graf
2011-09-29 19:28 ` Blue Swirl
2011-09-29 21:19 ` Alexander Graf
2011-09-25 19:50 ` Anthony Liguori
2011-09-30 3:21 ` Stefan Berger
2011-09-30 12:59 ` Anthony Liguori
2011-09-30 14:05 ` Stefan Berger
2011-10-10 12:14 ` Max Filippov
-- strict thread matches above, loose matches on Subject: below --
2011-09-24 21:56 Anthony Liguori
2011-09-25 16:28 ` Blue Swirl
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=4E7A828A.3030404@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 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).