Bug Parade Countdown: The ice is coming, but not here yet

Justin Obara obara.justin at gmail.com
Mon Dec 13 15:08:50 UTC 2010

Here's what I think our plan should be for today.

1) Get in any commits and finish off all blockers

2) Code Review, starting with framework changes

3) Perform any codebase wide general tasks (e.g. removing DOS  line endings)

4) Perform any other general tasks

5) Start testing where possible.

Once all the code is in, and the framework reviews and codebase wide general tasks are done, we should be able to start testing components that have  no more changes left. Meaning there will still be code review and some general tasks for  some components, but the ones that are ready for testing we should get a start on.

Note that the above don't necessarily have to happen in that order, but that is the priority. For example, 3) can probably happen at any time before 5).

- Justin
On 2010-12-12, at 11:06 PM, Colin Clark wrote:

> Hi Justin,
> Here's an update on the issues I've been working on from your freeze countdown list:
> On 2010-12-10, at 9:33 AM, Justin Obara wrote:
>> 	• Implement Uploader backwards compatibility
> I've attached a patch to http://issues.fluidproject.org/browse/FLUID-3885 with a working implementation of transformation expanders, which allow us to convert old-style Uploader options to the new format. I haven't yet committed this code, but I expect to have it all working and in trunk tomorrow morning. My plan is to wire this up to the Uploader via IoC, ensuring that only users who include a special "Uploader 1.3 compatibility" file will have their options transformed in this way.
>> 	• Write progressive enhancement unit tests
> I committed unit tests for the new progressive enhancement framework functions yesterday and they were reviewed by Michelle. The overall implementation still needs review, which I will include in a mega review session with Michelle, Antranig, Mike and I tomorrow.
> http://issues.fluidproject.org/browse/FLUID-3872
>> 	• Finish code reviews, and any code changes needed
> My goal tomorrow is to spend the entire day doing code review, as soon as FLUID-3885 has been committed. Given the amount of review left to do, I expect we'll have to delay the release by a day to get it all done before we start QA testing. We could start on testing without finishing code reviews, but I'm hesitant to do so in case any non-trivial code changes emerge from the review process. What do you think?
> Colin
> ---
> Colin Clark
> Technical Lead, Fluid Project
> http://fluidproject.org

More information about the fluid-work mailing list