On 10/11/2011 06:36 AM, Paolo Bonzini wrote:
On 10/10/2011 01:35 PM, Juan Quintela wrote:
Hi
Please send in any agenda items you are interested in covering.
Planning the feature freeze:
- what is left to merge?
- test day?
Great topic. Just a reminder, we're looking at release dates of:
| 2011-10-15
| Soft freeze
|-
| 2011-11-01
| Hard master
|-
| 2011-11-07
| Tag qemu-1.0-rc1
|-
| 2011-11-14
| Tag qemu-1.0-rc2
|-
| 2011-11-21
| Tag qemu-1.0-rc3
|-
| 2011-11-28
| Tag qemu-1.0-rc4
|-
| 2011-12-01
| Tag qemu-1.0
Soft Freeze FAQ:
== 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].
Regards,
Anthony Liguori
Paolo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
