Hi, Release criteria discussion has been closed and wiki has been updated accordingly by Brian [1][2]. Release management for 3.6.0 [3] has been updated with the accepted changes in release criteria. ACTION: Feature proposed for 3.6.0 must now be collected in the 3.6 Google doc [4] and reviewed by maintainers. Finished the review process, the remaining key milestones for this release will be scheduled. For reference, external project schedules we're tracking are: Fedora 21: 2014-12-09 (RELEASED) Fedora 22: no earlier than 2015-05-19 Foreman 1.8.0: 2015-03-01 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 and we can also add 3) keep current 6 months cycle The tracker bug for 3.6.0 [6] currently shows no blockers. There are 460 bugs [7] targeted to 3.6.0. Excluding node and documentation bugs we have 436 bugs [8] targeted to 3.6.0. [1] http://www.ovirt.org/Release_Criteria_Template [2] http://www.ovirt.org/Release_process [3] http://www.ovirt.org/OVirt_3.6_Release_Management [4] http://goo.gl/9X3G49 [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 -- Sandro Bonazzola Better technology. Faster innovation. Powered by community collaboration. See how it works at redhat.com