[Chandler-dev] RC1 and validation testing : Please read!

[Reid Ellis]

Do we delete the results already there so as to start with a clean  
slate? e.g., do I clear out the "Status/Remark" column at  <http:// 
chandlerproject.org/Projects/TriageTestSpec>?  Or should I just  
gradually replace them with more up-to-date info, in which case all  
status items should have an r# associated with them?

Reid

On Aug 23, 2007, at 17:19, Philippe Bossut wrote:
> Hi,
>
> We had a short meeting @ 1pm and with the fix of bug 10595 dropping  
> in, we decided to cut our first Desktop RC1. Bear will be tagging  
> the release and build. The tree will be frozen for a couple of  
> hours (see Bear's email).
>
> When that's done, we will sanity check (QA) which will take a  
> couple of days. When done (and if successful), we'll make that RC1  
> available for download. The consensus is that, even if not fully  
> qualified, this version is better than Desktop 0.6.1 and we prefer  
> new users picking up that RC1 to an old version. We'll mark  
> *clearly* that this RC is *not* the certified final release and  
> that tests are still in progress. The important thing is that this  
> will allow Hub to move forward with upgrading to Cosmo 0.7.0.
>
> While this is happening, we need to pass the whole battery of tests  
> on RC1 to fully qualify the release. We need the help of *everyone*  
> here so, to make attributions clear, we created a matrix of test  
> plan / assignments here:
>   http://chandlerproject.org/Projects/ 
> ChandlerDesktopTestSpecifications
>
> Some 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.
>
> Questions on the test plan can be sent to Aparna, me or asked on  
> IRC (#chandler).
>
> Cheers,
> - Philippe