Hi, Release criteria discussion has been closed with last week oVirt sync meeting [1]. Release management for 3.6.0 [2] will soon be updated with the accepted changes in release criteria. The remaining key milestones for this release must now be scheduled. For reference, external project schedules we're tracking are: 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 [3]: 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 [4] and reviewed by maintainers. The tracker bug for 3.6.0 [5] currently shows no blockers. There are 453 bugs [6] targeted to 3.6.0. Excluding node and documentation bugs we have 430 bugs [7] targeted to 3.6.0. [1] http://resources.ovirt.org/meetings/ovirt/2014/ovirt.2014-11-26-15.07.log... [2] http://www.ovirt.org/OVirt_3.6_Release_Management [3] http://lists.ovirt.org/pipermail/users/2014-November/028875.html [4] http://goo.gl/9X3G49 [5] https://bugzilla.redhat.com/show_bug.cgi?id=1155425 [6] http://goo.gl/zwkF3r [7] http://goo.gl/ZbUiMc -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com