[ovirt-users] [QE][ACTION REQUIRED] oVirt 3.6.0 status

Sandro Bonazzola sbonazzo at redhat.com
Wed Nov 19 02:52:10 EST 2014


Release criteria discussion started on 2014-10-22 and should have ended last week as per current release process [1].
Since oVirt sync meeting wasn't held last week, it has been postponed to today 2014-11-19.

Current options are:
1) keeping the same release criteria we had for 3.5 [2]
2) review the proposed changes [3] and prepare new release criteria for 3.6

Release management for 3.6.0 has been created [4]
The key milestones for this release must be scheduled:

Key Milestones
    Release criteria discussion start: 2014-10-22
    Release criteria ready: 2014-11-19
    Feature freeze: 60 Days before release
    First Test Day: 45 days before release
    Release Candidate: 30 days before release
    Release: 6 months after oVirt 3.5.0 release

External Project Schedules
    Fedora 21: 2014-12-09
    Fedora 22: 2015-XX-XX
    GlusterFS 3.7: 2015-04-29
    OpenStack Kilo: 2015-04-30

Two different proposals have been made about above scheduling [5]:
1) extend the cycle to 10 months for allowing to include a large feature set
2) reduce the cycle to less than 6 months and split features over 3.6 and 3.7

Feature proposed for 3.6.0 must now be collected in the 3.6 google doc [9]
and reviewed by maintainers.

A tracker bug for 3.6.0 has been created [6] and currently shows no blockers.

There are 412 bugs [7] targeted to 3.6.0.
Excluding node and documentation bugs we have 392 bugs [8] targeted to 3.6.0.

[1] http://www.ovirt.org/Release_process
[2] http://www.ovirt.org/OVirt_3.5_release-management#Release_Criteria
[3] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html
[4] http://www.ovirt.org/OVirt_3.6_Release_Management
[5] http://lists.ovirt.org/pipermail/users/2014-November/028875.html
[6] https://bugzilla.redhat.com/show_bug.cgi?id=1155425
[7] http://goo.gl/zwkF3r
[8] http://goo.gl/ZbUiMc
[9] http://goo.gl/9X3G49

Sandro Bonazzola
Better technology. Faster innovation. Powered by community collaboration.
See how it works at redhat.com

More information about the Users mailing list