Community
Participate
Working Groups
Establish the exit QA Criteria for each iteration going forward. These criteria need to be applied to ALL iterations going forward starting with i9. If feasible, these criteria should also be considered for i8; however, this may be a bit too ambitious.
We need to reinforce that, adoptability, as discussed in the Detroit F2F, is a key quality metric for COSMOS 1.0. We also need to specify operating efficiency related quality expectations within the COSMOS 1.0 timeframe. As there are multiple and different characteristics, e.g. Concurrency / Availability / Performance, we need to identify which of these can be addressed by which iteration.
Design submitted for review; awaiting feedback.
1. COSMOS 1.0 goes live on June 27, 2008. As of this writing, there are THREE remaining iterations, i.e. i9, 10, and i11. Thus, the next “big” date is March 7, 2008, which is when i9 ends. I10 ends on May 2, 2008 and the final iteration, i11, ends on June 27, 2008. 2.The plan is to complete http://wiki.eclipse.org/index.php/COSMOS_QA_Criteria by the first week of February 2008 and run i9 QA based on this document which details the COSMOS 1.0 QA Expectations. 3. If QA feels that these criteria are lacking in anyway as a result of reviews and the i9 QA effort, we have i10 to do further updates and another round of fixes to http://wiki.eclipse.org/index.php/COSMOS_QA_Criteria via an i10 ER. 3. It is strongly desired that the QA Expectations must be very clearly defined AND finalized via actual iteration runs by the end of i10.
This is closed...
Even though this is closed, can the wiki document be updated? I'm still not sure if testing our tooling is part of the QA plan currently. It hasn't been in previous iterations.
