Hello everyone, We are now one month away from Bexar BranchMergeProposalFreeze[1].
[1] http://wiki.openstack.org/BranchMergeProposalFreeze With 36 blueprints, the list we currently have targeted for Nova bexar[2] does not accurately represent what we think we can announce and track as feature targets for the bexar release. Rick and I need to clean it up and make sure it contains reasonable objectives that we are confident we can deliver in that release. [2] https://blueprints.launchpad.net/nova/bexar The best way to do this is to start from a clean slate, discuss in the next week(s) with the blueprint assignees what can be coded in the next month, and add back to the list only those specs that we have reasonable confidence with. I will therefore in the next hours "decline for bexar" all the specs that are in the Nova/Bexar list, to come up with an empty list. Then we'll gradually add the confirmed blueprints back in the list, so that from now on, the list only contains confirmed targets. This does *not* mean your feature has been refused for Bexar. Please note that the fact a specific blueprint is (or is not) in the nova/bexar list does not affect in any way your ability to code and merge another feature into Bexar. The list just represent what we communicate to our stakeholders and what, as a result, we follow on more closely during our team meetings. In order to avoid me pinging you about progress, you might actually prefer not to be in the list :) Feel free to ask me any question about this. -- Thierry Carrez Release Manager, OpenStack _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : [email protected] Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
