Hi team! During the OpenStack team meeting today (tuesday) Thierry and I briefly chatted about our concerns around the large number of blueprints assigned to G-3 for Quantum.
I describe our existing plan of having core devs focus their efforts on any 'high' or above blueprints and bugs, and treating medium issues as "best effort" based on your own judgement of the value they provide to the project. If there's something at 'medium' that we all agree needs to be 'high', we can definitely have that discussion as a team. One item Thierry pointed out is that we need to make sure that core devs also have enough cycles to focus on test + bug fixes toward the end of G-3, which needs to be a team priority. We need to prepare everyone for the fact that many of the medium priority blueprints proposed for G-3, even if completed from a code perspective, may well not merge because the core team needs to focus on platform stability and a small set of 'high' features that apply to the whole community. During this period, we'll also need to make sure that review quality stays high, as the last thing I want is a slew of post G-3 bug fixes due to features we prematurely merged right before the G-3 window closed. We need that time for testing/bugfixing/docs/etc. Please ping the core team alias if additional questions/concerns pop up due to the large number of G-3 blueprints. We're somewhat in un-charted territory, so we'll need to work together to make sure we deliver a SOLID grizzly release, even if it means not getting a some of the 'medium' features. Dan -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~quantum-core Post to : [email protected] Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
