Planning/SoftFeatureFreeze: Difference between revisions
(Created page with '== 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…') |
(updated description of softfreeze based on Anthony's email) |
||
| Line 1: | Line 1: | ||
== What is the soft feature freeze? == | == 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 | 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 non-trivial feature should have some code posted to the qemu-devel mailing list if it's targeting a given release. Major features, and in particular features with a high likelihood of breaking things, should already be in the process of being merged. | ||
== What should I do by the soft feature freeze? == | == What should I do by the soft feature freeze? == | ||
Revision as of 14:31, 18 October 2013
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 non-trivial feature should have some code posted to the qemu-devel mailing list if it's targeting a given release. Major features, and in particular features with a high likelihood of breaking things, should already be in the process of being merged.
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[1].