Hello,
I think this is a reasonable request. We have given ourselves a little
bit of leeway for this release, by scheduling the release for a
Wednesday. I agree that it will better to ship a day or two late and
have a better working product to show for it.
- Justin
On 15-Dec-08, at 1:58 AM, Colin Clark wrote:
Hi Justin,
I have an idea that I wanted to float past you and others in the
community...
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 we've identified.
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?
Colin
---
Colin Clark
Technical Lead, Fluid Project
Adaptive Technology Resource Centre, University of Toronto
http://fluidproject.org
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
