Difference between revisions of "QA Camp"
JoostAndrae (talk | contribs) m |
JoostAndrae (talk | contribs) |
||
Line 15: | Line 15: | ||
Maybe you'll attend to this event and you want to add a topic.<br> | Maybe you'll attend to this event and you want to add a topic.<br> | ||
QA members who already worked on childworkspaces and those who were actively involved into application specific QA and testing are invited to bring-in their knowledge. | QA members who already worked on childworkspaces and those who were actively involved into application specific QA and testing are invited to bring-in their knowledge. | ||
+ | |||
+ | === Details regarding discussion topics === | ||
+ | ==== Discussing the "Lots of UNCONFIRMED DEFECT-issues" thread (just an excerpt)==== | ||
+ | <strong>Mechtilde Stehmann:</strong> "I also try to do some issues a day but there are many issues where the reporter doesn't answer. So if I touch that issues the next time i set them to invalid and close them."<br> | ||
+ | <strong>Stefan Weigel:</strong> "I do observe an additional problem:<br> | ||
+ | A big part of those unconfirmed issues turn out to be a support case rather than a topic that should be handled by IssueTracker. This leads to an overload of IssueTracker and QA manpower. I don´t know, what can be done, to make people ask and discuss their problem in a forum or on a mailing list before filing an issue."<br> | ||
+ | <strong>Joost Andrae:</strong> I can second this. Maybe using some sort of text template for this type of "support request" might be useful. Unfortunately each of these issues need to be worked on.<br> | ||
+ | <strong>Marcus Lange:</strong> | ||
+ | when it's really a support request (e.g., how to make text bold, my printer doesn't print, etc.) then we could point the user to the user@ooo mailing list with a explaining text and finaly close the issue.<br> |
Revision as of 12:54, 14 October 2009
QA Camp at the OpenOffice.org Conference 2009 in Orvieto, Italy
Details about this event
QA Camp
Building: Palazzo dei Sette
Room: Sette 2
Date: 2009-11-05 04:15 PM -- 07:00 PM
Ideas about topics to discuss and about things to be done
- talk about QA topics in general
- talking about hot topics like the "Lots of UNCONFIRMED DEFECT-issues" thread within the QA mailing list
- talking about iTeams and childworkspaces work (eg. to QA a CWS)
- talking about application specific QA
- how to strengthen communication between native language teams (QA related/ native language/l10n QA teams) and the "global" QA project ?
Maybe you'll attend to this event and you want to add a topic.
QA members who already worked on childworkspaces and those who were actively involved into application specific QA and testing are invited to bring-in their knowledge.
Details regarding discussion topics
Discussing the "Lots of UNCONFIRMED DEFECT-issues" thread (just an excerpt)
Mechtilde Stehmann: "I also try to do some issues a day but there are many issues where the reporter doesn't answer. So if I touch that issues the next time i set them to invalid and close them."
Stefan Weigel: "I do observe an additional problem:
A big part of those unconfirmed issues turn out to be a support case rather than a topic that should be handled by IssueTracker. This leads to an overload of IssueTracker and QA manpower. I don´t know, what can be done, to make people ask and discuss their problem in a forum or on a mailing list before filing an issue."
Joost Andrae: I can second this. Maybe using some sort of text template for this type of "support request" might be useful. Unfortunately each of these issues need to be worked on.
Marcus Lange:
when it's really a support request (e.g., how to make text bold, my printer doesn't print, etc.) then we could point the user to the user@ooo mailing list with a explaining text and finaly close the issue.