Hi, Here are a few reminders around the Mitaka release, and info about the blueprint freeze exception process.
Dates ----- January 21st: Nova non-priority feature freeze (Thats the deadline for merging the code into master) December 8th and 9th: Virtual API document sprint http://lists.openstack.org/pipermail/openstack-dev/2015-November/079220.html December 17th: non-priority feature review bash day More details, please see: https://wiki.openstack.org/wiki/Nova/Mitaka_Release_Schedule (yes, I will get that uploaded to the central location) Reno ------ As you probably already spotted, for both nova and python-novaclient, all release notes are now published using Reno. For more details, please see: http://docs.openstack.org/developer/nova/code-review.html#release-notes Reviews ------- Lets keep focusing on these reviews: https://etherpad.openstack.org/p/mitaka-nova-priorities-tracking As always, good quality reviews from non-cores is vital: https://wiki.openstack.org/wiki/Nova/Mentoring#Why_do_code_reviews_if_I_am_not_in_nova-core.3F As previously mentioned, nova-core are actively mentoring folks to help improve their review skills. It is this hard work (on both sides) that lead to bauzas and alex_xu joining nova-core. Lets keep all forms of mentoring going! Freeze Exceptions ------------------ All blueprints for Mitaka should now be approved in launchpad, with the appropriate specs merged. So you have a spec (or specless blueprint) up for review, here is what you need to know... * We have over 120 blueprints already approved for Mitaka. * Its likely only 60-70 blueprints will be completed during Mitaka. * Please note, the non-priority feature freeze is on January 21st. * In fairness to all, the exceptions must be... exceptional. Preference will be given to specs and specless blueprints that are: * part of a priority effort * already had significant amounts of review The deadlines for this process will be: * Must add to etherpad by end of 9th December * Must be approved/merged by end of 11th December * Spec approval tracked in gerrit, two +2s to merge spec With all that in mind, if you want to apply for an exception, please add a link to your spec in the top of this etherpad, where it says "Exception Requests": https://etherpad.openstack.org/p/mitaka-nova-spec-review-tracking Please note: Bugs that need API changes, and so need a spec, are not affected by the blueprint freeze. They should be fixing a bug, not adding new functionality. As ever, any questions, please do ask via email, IRC, etc. Thanks, johnthetubaguy __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev