<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->

<!-- If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If you feature is not completed in time we want to assure others that other parts of Fedora will not be in jeopardy. -->

−

I'm working on test rebuilds of all affected packages; I plan to commit the proposed changes to "python3.3" branches of dist-git, so that everything is ready and any major issues should have been shaken out before we "pull the trigger" and commit/build for real into f18.

+

I'm working on test rebuilds of all affected packages, using skvidal's [http://fedorapeople.org/gitweb?p=skvidal/public_git/scripts.git;f=mock/mockchain.py;h=deb4f0a4f7c162d7222fdf43da92b77c04659a25;hb=HEAD mockchain] tool (this also gives us a build ordering, by grepping the logs).

+

+

I plan to commit any proposed changes to "python3.3" branches of dist-git, and then merge to master when we do it for real.

+

+

This pre-planning should mean everything is ready and any major issues should have been shaken out before we "pull the trigger" and commit/build for real into f18.