Features/Policy: Difference between revisions
| Line 132: | Line 132: | ||
* New features may be proposed (using the guidelines above) and accepted no later than the ''Feature Acceptance'' milestone. Of course you can still propose a feature for an upcoming release. | * New features may be proposed (using the guidelines above) and accepted no later than the ''Feature Acceptance'' milestone. Of course you can still propose a feature for an upcoming release. | ||
* New features must be feature complete or close enough to completion by ''Feature Freeze'' that a majority of its functionality can be suitably tested--the "feature is testable". | * New features must be feature complete or close enough to completion by ''Feature Freeze'' that a majority of its functionality can be suitably tested--the "feature is testable". | ||
* All feature must be present in the release after Feature Freeze. | |||
* After the release at ''Feature Freeze'' all features will be evaluated based on test results to date. | * After the release at ''Feature Freeze'' all features will be evaluated based on test results to date. | ||
* Possible reversion of a feature is latest at the ''UI Freeze'' release. | * Possible reversion of a feature is latest at the ''UI Freeze'' release. | ||