oVirt 4.1 Release Management
Key Milestones
Date | Milestone |
---|---|
2016-12-01 | oVirt 4.1 Beta1 - Feature Freeze |
2016-12-21 | oVirt 4.1 Beta2 - String Freeze - Stable branch creation |
2017-01-23 | oVirt 4.1 RC1 |
2017-01-26 | oVirt 4.1 RC2 |
2017-02-01 | oVirt 4.1 GA Release |
Translation Status
Translations are handled by Zanata. You can join the translators team and see current translation status here: https://translate.zanata.org/zanata/iteration/view/ovirt/master/languages
Release Criteria
Alpha Release Criteria
- MUST: All sources must be available on ovirt.org
- MUST: All packages listed by subprojects must be available in the repository
Beta Release Criteria
- MUST: Release Notes have feature-specific information: oVirt 4.1 Release Notes
- MUST: Alpha Release Criteria are met
- MUST: Supported localizations must be at least at 70% of completeness for being included in the release
- MUST: All accepted features must be substantially complete and in a testable state and enabled by default – if so specified by the change
Candidate Release Criteria
- MUST: Beta Release Criteria are met
- MUST: All test cases defined for each accepted feature must be verified and pass the test for the build to be released
- MUST: All lower-level components must be available on supported distributions at required version [1]
- MUST: No known regressions from previous releases should be present
- MUST: Each subproject must allow upgrade from a previous version, either providing documented manual or automated upgrade procedures
- MUST: All features working on previous release must still work in the new release if not dropped as deprecated