[Chandler-dev] RC2 and Test Assignment

[Philippe Bossut]

Hi,

As you certainly already know, we created and posted last week Chandler 
Desktop RC1. This is now the "default" version new users find on our 
download web page 
(http://chandlerproject.org/Projects/DownloadChandlerDesktop) so we're 
expecting to see more and more people pitching in with new bugs. We've 
seen some of it already in Bugzilla reports from external users, posting 
on the user list and people showing up on IRC. This is good!

We're currently cutting a Chandler Desktop RC2 and will certainly cut an 
RC3 within a day or 2 now (we have couple of bugs in the pipe already). 
Though we're still not completely and officially done, this is looking 
pretty good and we've been hitting ZBR a couple of time already (which 
is the reason why this point is sometimes known as ZBB aka Zero Bug 
Bounce...).

While this is great and make the final official RC within reach, we 
decided to put the date of the official release to Monday September 
10th. That's the date we'll put on various places on our wiki and that's 
a date that we don't want to change again ever (baring catastrophic 
unstability but after months of debug, I can't see that happening 
really...). Being early won't hurt though so there's no reason to slow 
down or take it easy: those last bugs we can identify and fix are still 
very valuable.

There's no change in plan as far as test plan coverage is concerned 
though which means: *devs are still assigned to test plans!*. Please 
look to your assignment here as it seems that quite a few of you didn't 
take notice:
  http://chandlerproject.org/Projects/ChandlerDesktopTestSpecifications

Notes:
- some plans are longer than others so, if you're done earlier, helping 
others is good...
- I made the attribution based on area knowledge (not necessarily the 
best choice, mind you, since the theory goes that the less you know 
about an area, the better you test) but I thought it'd be more efficient 
that way. If you feel unconfortable with the choice and wish to change, 
you can switch with someone else, you can't bail out entirely though.
- the total amount of time to run the whole enchillada is basically 1 
week, i.e., it doesn't need to be done by Monday...
- logged bugs will be triaged by Bug Council and may result in fix and 
another RC to be cut
- we do not expect to run all the test on the 4 platforms. If you can 
test on several platforms, great, if you can't that's ok too. Mention 
the platforms you tested with in the wiki test plan. Testing at least 
once on one platform is what we're aiming for.
- please do not erase the existing test status in the table so that QA 
can keep track of the history of tests

Questions on the test plan can be sent to Aparna, me or asked on IRC 
(#chandler).

Cheers,
- Philippe