Authors:

oVirt 3.6 Release Management

Key Milestones

| Date | Milestone | |—|—| | 2014-10-17 | oVirt 3.5.0 GA Releases | | 2014-10-22 | Release criteria discussion start | | 2014-11-12
2014-11-19
2014-11-26 | Release criteria ready | | 2015-04-22 | Feature Review - Feature Submission Closed | | 2015-05-06

2015-05-12

2015-05-19 | Alpha Release: oVirt 3.6 Release Notes | | 2015-05-12

2015-05-19 2015-05-26 2015-05-27

| Alpha Release Test Day | | 2015-06-15 | Feature freeze | | 2015-06-17

2015-06-24 2015-06-25 2015-06-26

2015-06-29 | Second Alpha Release: oVirt 3.6 Release Notes | | 2015-07-28 | Third Alpha Release: oVirt 3.6 Release Notes | | 2015-07-15 2015-08-03 | Beta Release | | 2015-07-20 2015-08-10 | Beta Release Test Day | | 2015-08-11 2015-08-14 | Second Beta Release | | 2015-08-03 2015-08-19 | String Freeze | | 2015-08-20 | Third Beta Release | | 2015-09-02 2015-09-07 | Fourth Beta Release | | 2015-09-09 | Fifth Beta Release | | 2015-09-16 | Sixth Beta Release | | 2015-08-19

2015-09-02 2015-09-16 2015-09-22

2015-09-28 | Release Candidate | | 2015-08-24

2015-09-08 2015-09-17 2015-09-24

| Release Candidate Test Day | | 2015-10-14 | Second Release Candidate | | 2015-10-21 | Third Release Candidate | | 2015-09-08

2015-09-22 2015-09-29 2015-10-12

2015-11-04 | Release |

NOTE this is a tentative planning according to Release process

External Project Schedules

Links to other significant project schedules, useful for seeing how oVirt aligns with them.

oVirt Live

oVirt Live has been rebased on EL7.

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

Key Proposed Changes

The following list is a subset of the features proposed for oVirt 3.6

Tracker Bug

    • Tracker: oVirt 3.6 release

Release Criteria

Alpha Release Criteria

  1. MUST: All sources must be available on ovirt.org
  2. MUST: All packages listed by subprojects must be available in the repository

Beta Release Criteria

  1. MUST: Release Notes have feature-specific information: oVirt 3.6 Release Notes
  2. MUST: Alpha Release Criteria are met
  3. MUST: Supported localizations must be at least at 70% of completeness for being included in the release
  4. 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

  1. MUST: Beta Release Criteria are met
  2. MUST: All test cases defined for each accepted feature must be verified and pass the test for the build to be released
  3. MUST: All lower-level components must be available on supported distributions at required version [1]
  4. MUST: No known regressions from previous releases should be present
  5. MUST: Each subproject must allow upgrade from a previous version, either providing documented manuals or automated upgrade procedures
  6. MUST: All features working on previous release must still work in the new release if not dropped as deprecated

[1] This means we’re not hosting any package we don’t develop inside oVirt repository just because it’s not yet released officially.