Easing into code freeze?
colin.clark at utoronto.ca
Mon Dec 15 06:58:19 UTC 2008
I have an idea that I wanted to float past you and others in the
This has been a whirlwind of a bug parade; Infusion 0.6 is packed full
of new features and bug fixes. As part of our process, we've been
careful to make sure each commit gets peer reviewed before being
accepted. Lots of interesting questions, and a few potential side
issues, have been raised throughout these reviews.
Given this, I'm wondering if it might be a good idea to transition a
bit more gradually into the code freeze period for Infusion 0.6. This
would give us a bit of extra time to continue to review code, discuss
the questions that have arisen, and address any final, minor issues
So, to do this, I'm thinking we would extend bug parade by one more
day (Monday), and then delay the 0.6 release by a day to give the QA
testers enough time to freeze and test. What do you think?
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
More information about the fluid-work