Issue hunting party

Today, 15th of July 2008, the first QA day should take place. Stefan Baltzer by Sun Microsystems QA team organized it and many community members

Working on 'fixed/verfied' issues

Working on fixed and verified issues (in a [CWS]), which are integrated into the product. A final check if there as still and also fixed in the final product is needed. If it is, than close the issue.

fixed and integrated issues in OOo 2.2.1 and older versions of OOo 2.x => starting number = 3

fixed and integrated issues in OOo 2.3/OOo 2.3.1 => starting number = 221

fixed and integrated issues in OOo 2.4/OOo 2.4.1 => starting number = 383

fixed and integrated issues on the way to OOo 3.0 => starting number = 889

Working on 'unconfirmed' defects

The QA team should take always a look at the unconfirmed defects. These are the new incoming issues, which aren't re-checked by a community member of the QA project. If the issue is valid it has to be set to state 'new'. Perhaps the summary should be adapted to a more feasible meaning and if possible the description should be shortened to a useful and clear description.

• unconfirmed defects in Framework => starting number = 412
• unconfirmed defects in Writer => starting number = 319
• unconfirmed defects in Spreadsheet/Chart => starting number = 295
• unconfirmed defects in Graphics (Presentation and Draw) => 26
• unconfirmed defects in Data Base => 49
• unconfirmed defects in other components => 281

Please take also a look at the blog by Thorsten Ziehm from Friday, 11th of July 2008. There you will find also links for the submission date of the 'unconfirmed' defects. http://blogs.sun.com/GullFOSS/entry/status_of_unconfirmed_defects_in

The overall starting number for today is : 1376

Issues which has to be clarified after the chat

• ...

Hint

• You can edit the query, when you click on the link in the list. After that scroll to the end of the list and click 'Edit this Query'. For example than you can add the 'component' of your choice.
• some issues are 'developer issues', which cannot be verified easily by a QA person. So do not invest so much work in such issues.
• issues from QA persons by Sun can be verified often more easily (who are the QA persons there?)
• it is better to start with the newest issues, because they aren't often checked by a QA until now; older 'unconfirmed' issues are often checked by many people, but nobody take the responsibility to close the issue or send it as valid issue to a developer