I think those dates should be okay. Ideally I'd like to have a longer bug period, but would rather have the time spent on making the new features as good as possible.

Here is what it might look like.

Possible Timeline for 1.0
----------------------------------

Bug Parade: March 17 - 23
Testing: March 24 - 27
Release: March 30 - 31

Does that look alright?

- Justin


On 3-Mar-09, at 11:50 AM, [email protected] wrote:

I think that is reasonable... as you know, I will be in Toronto
for that week 10-17, and imagine we will want to spend a good proportion
of the time consolidating the new features we have planned. If we
can squash a few bugs too, so much the better :)

Cheers,
Boz.


Quoting Colin Clark <[email protected]>:

Hi everyone,

Let's talk about the timing for our Infusion 1.0 release. As a
starting point, Justin threw these proposed dates:

On 25-Feb-09, at 11:51 AM, Justin Obara wrote:

Possible Timeline for 1.0
----------------------------------

Bug Parade: March 10 - 23
Testing: March 24 - 27
Release: March 30 - 31


I think Justin's is rightfully anticipating a wave of new features in
1.0, and wants to make sure we have enough time to test
comprehensively and fix any lingering bugs.

On the other hand, we're going to want to balance this with enough
time to develop these new features. Also, let's keep in mind that
we're anticipating an Infusion 1.1 release in April, so we'll have an
opportunity to cycle back and fix smaller bugs or add those missing
features then.

Off the top of my head, I'm wondering about pushing bug parade to
March 17. Thoughts? Other suggestions?

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





----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work

Reply via email to