As promised during yesterdays meeting, a quick summary of the situation around feature freeze (FF) and the live migration branch.
All the major feature branches now landed with the notable exception of the live-migration branch. There might still be a few "default behavior change" branches that also need FF exceptions, but that means you can safely switch to high QA gear and fix as many bugs as you can. Mostly due to collective failure to sufficiently review the live-migration branch in time, we had to revert the live migration branch changes in trunk. The branch still has a standing FF exception to be reproposed and merged in Bexar. However the time is running very short: if a new branch fixing all the issues raised by termie (including the lack of unit tests) can be proposed by Thursday and if it passes all reviews by Friday, we will accept it for merging before the end of the week. If it misses any of those (UTC) deadlines, then it's off the table and deferred to Cactus. We can't afford to merge a database schema change later without seriously jeopardizing Bexar QA. Personally I'd prefer if the whole feature was calmly prepared and baked in a branch over the next weeks, proposed when Cactus opens after February 4, and reviewed/merged early then. It sounds much saner than rushing the writing of feature test code two weeks before a release. But I also understand that it would be a bit unfair to masumotok and NTT Data, who proposed their branch early and worked a lot recently on fixing the issues we raised. So I'll leave the choice between "still trying" and "deferring" to them. Regards, -- Thierry Carrez (ttx) 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
