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

Sandro Bonazzola sbonazzo at redhat.com
Wed Nov 26 03:31:17 EST 2014


Release criteria discussion started on 2014-10-22 and will end today 2014-11-26 as discussed in last oVirt sync meeting [1].

If no objections will be raised, the proposed changes [2] will be accepted.

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

Key Milestones
    Release criteria discussion start: 2014-10-22
    Release criteria ready: 2014-11-26
    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 [4]:
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 [8]
and reviewed by maintainers.

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

There are 439 bugs [6] targeted to 3.6.0.
Excluding node and documentation bugs we have 419 bugs [7] targeted to 3.6.0.

[1] http://resources.ovirt.org/meetings/ovirt/2014/ovirt.2014-11-19-15.01.log.html
[2] http://lists.ovirt.org/pipermail/devel/2014-September/008695.html
[3] http://www.ovirt.org/OVirt_3.6_Release_Management
[4] http://lists.ovirt.org/pipermail/users/2014-November/028875.html
[5] https://bugzilla.redhat.com/show_bug.cgi?id=1155425
[6] http://goo.gl/zwkF3r
[7] http://goo.gl/ZbUiMc
[8] 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