Hello Stefan, Thorsten, Florian Many thanks for good IRC session, and report. I wonder whether Stefan can blog it at GullFOSS. Florian, you have blogged Stefan's announce, so this e-mail should also be blogged. what do you think?
Best, From: Stefan Baltzer <[email protected]> Subject: [qa-dev] IRC Issue hunting session of Jan 13th, 2009 Date: Thu, 15 Jan 2009 17:47:47 +0100 > Hi, everybody! > > WHAT > Again, we had a 24hour issue cleanup session. > Based on a OOO300_m15 build (OOo 3.01 ReleaseCandidate2), we focussed on > "open, verified, Target 3.01" issues. > > WHO > First, a big THANK YOU to those who were actively involved, especially those > participating for the first time. > I would like to thank RedFlagLimeiying and RedFlagZhulihua (for staying up > that late :-) as well as Sophie, André, Cloph, Gilles and Pavel for actively > helping along this time. > And of course I am pleased to welcome Gilles (gibi) within the "inner circle" > as he got the "CanConfirm" rights during this session. > > PROBLEMS > Unfortunately, we had no official announcement of a complete and successful > upload of the m15 build before the session started. > A delay of a build or upload or distribution might always happen and a shift > of the broadly announced session did not sound feasible. > But the most important install sets were available in time so that we had a > common base to re-verify the issues fixed for 3.0.1 > > NUMBERS > The amount of open 3.01 issues we closed within the 24 hours was 45. > A bit more detailed (Component: [start value] -> [end value] = [change]): > > Writer: 43 -> 13 = down 30 > Calc/Chart: 11 -> 0 = down 11 > Draw/Impress 13 -> 12 = down 1 > Installation 24 -> 20 = down 2 > Other 11 -> 10 = down 1 > > In the Base and Automation issue area, no issues got proceeded that day. The > respective specialists could not join but would have been needed for that. > > RESULTS > The main outcome is that we have found no "failed" issues. > This means that the concept and processes of CWS (Child Work Space) worked > well as well as the aim to get only a limited amount of "needed" fixes into > OOo 3.01 > > SUCCESS? > Beside reducing the amount of open issues, my aim was also to have people > TRYING to deal with issues and ask for help and get it within this session. > This did happen and hopefully brought some people a better understanding of > how to proceed issues. > > AGAIN: NUMBERS > OOo is a successful thing with hundreds of millions of users. Very good. > Within this huge Open Source project, it is very easy to submit issues. > Now guess what many of these millions of users do. > They do submit issues! :-) > > In his recent blog, Thorsten Ziehm wrote about issue statistics, please read > http://blogs.sun.com/GullFOSS/entry/what_was_done_for_openoffice > > Summarized: In the year 2008, around 12000 issues were newly written and 4000 > got fixed. > This underlines that processing issues is an ever-lasting task for QA. > > Let me explain this connection: > In a perfect world (read: theoretically), the QA will handle ALL ISSUES at > least once: > (1) Read, understand, reproduce, comment, close it or pass it on, next issue > please > > In the case of an issue getting fixed (Yes, this DOES happen :-), it will be > at least 2 times more: > (2) Read, understand, reproduce problem in older version verify a fix in CWS > (3) Read, understand, reproduce problem in older version verify a fix in > Master build and close it. > > This makes an estimated 20000 issue "touches" by QA per year. > > Note that some issues need to be handled x-fold because different > environments/pre-conditions. > Note that some feature issues are in fact "construction sites" hiding behind > a single issue ID. And some of those are the work of weeks or months of > more-than-one person. > > CONCLUSION (1) > It looks like we need a daily issue hunting day in order to keep control on > the pure number of open issues. > > CONCLUSION (2) > It looks like more people need to get convinced to contributing to QA work. > What was that again? Finding issues? NOT finding issues? > > Most important QA work is communication. > The issue-related communication in this project is mainly done in the issue > tracker. > > Having a browser and an OOo version installed makes you ready for joining QA. > Because you can help > > (A) Reduce numbers of issues > -> closing invalid, fixed and duplicate ones > > (B) Sort issues > -> by correcting flags, summary and description (if needed) and > assigning to the correct developer (or component) > -> by proposing which ones to be fixed first/next/later > > But note that DECISIONS about developer resources are NOT made by QA. > So joining is not automatically a free ticket for your pet issue. > > But getting to know rules and people my help how to get things moved. > I like to move it. Do you? > > Have a nice day! > > Regards, > Stefan (QA Writer) > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
