Hi!
You may remember that I triggered the 24h issue meetings that we held in
the past. We decided that those events were not as effective as we hoped:
- The "marketing" and organisation were too much compared to the
outcome in numbers (around 100 per monthly party).
- The amount of active participants did not cover all applications
- Too many people I sort of "counted on" could NOT arrange it at that
very day.
So we believe that a "constant issue hunt" like this will bring much
more people into the race. We have a constant "flow" of issues so this
needs constant efforts.
Chris writes "A week or two" - Yes, each of you, once per quarter. That
will cover the whole year.
Oh, you can't do it on a Tuesday morning? - Try Friday and the IRC for
the tricky ones and do some "no-brainers" on Saturday night.
I am almost always in IRC while I am at work (stefan_b). So you have a
fair chance to get quick responses from me (or the folks I can quickly
get in for help) when it is needed for the issues you try to proceed.
So I invite all of you to post on the #qa channel when you are dealing
with issues from the list. Those without CanConfirm rights can get fast
assistance to get their processed issues closed.
I also think of "subjects of the day" - This depends on who is available
at the very moment.
What I already do is to invite a developer for a short discussion. Some
of those who probably can help do work the whole day and do not run
their chat client at all for weeks.
So if all this gets the community response we hope it does, you will see
and read more of my QA colleagues, too. They will very likely be more
present in IRC instead of staying out in favor of processing all their
issues on their own.
QA is communication. If our communication gets more effective, then the
product (and the mood!) will win in the long run.
But do not forget that "pushing/sorting/processing" issues is a much
bigger QA part than wasting energy to raise attention for your pet
peeve. The bug YOU find is ALWAYS the worst one. This is a kind of
natural law. Get over this and you do QA.
Regards,
Stefan Baltzer
QA Writer
limeiying wrote:
Hi Christoph,
+1.
I'm gonna take part in closing verified issues in IssueTracker.
I remember there are a lot of verified issues closing through IRC conference,
but now it seems to be waiting for IRC conference, :-）
Christoph Lukasiak said:
moin oo testing folks,
please support the OOo QA with closing verified issues .. we have 664 at
the moment and a big need to extreme reducing them .. they have to be
rechecked, because of eventually appearing regressions and to assure the
code quality ..
.. please stop to whine about the version for a while and start to
support the qa by improving the quality, for a week or two :)
howto:
1. install a dev 3.1 build from:
http://download.openoffice.org/next/index.html
2. open issue query:
http://qa.openoffice.org/issues/buglist.cgi?issue_type=DEFECT&issue_type=ENHANCEMENT&issue_type=FEATURE&issue_type=PATCH&issue_status=VERIFIED&target_milestone=OOo+3.1&email1=&emailtype1=exact&emailassigned_to1=1&email2=&emailtype2=exact&emailreporter2=1&issueidtype=include&issue_id=&changedin=&votes=&chfieldfrom=&chfieldto=&chfieldvalue=&short_desc=&short_desc_type=allwords&long_desc=&long_desc_type=allwords&issue_file_loc=&issue_file_loc_type=fulltext&status_whiteboard=&status_whiteboard_type=fulltext&keywords=&keywords_type=anytokens&field0-0-0=noop&type0-0-0=noop&value0-0-0=&cmdtype=doit&order=Reuse+same+sort+as+last+time&Submit+query=Submit+query
3a. guys without canconfirm rights: check if issue is fixed - if yes:
write something like 'verified in master version xy', if not contact the
corresponding application team lead
(http://wiki.services.openoffice.org/wiki/Team_Leads) and write a
comment into the issue.
3b. guys with canconfirm rights: you should know what to do (3a. ;) and
close the issue afterwards & also have a look at other issues and also
close them if they are verified.
p.s. if you do not understand an issue description, do not have the
equipment or knowledge for the issue etc. try the next one (there are
issues for every level ;)
bye chris
(http://wiki.services.openoffice.org/wiki/User:Clu)
Best wishes!
------------------
Li Meiying
Beijing Redflag 2000 Software CO.,LTD
MSN:[email protected]
Email:[email protected]
Tel:51570010-6140
Date:2009-03-26
To subscribe to the list, send a message to:
<[email protected]>
To remove your address from the list, send a message to:
<[email protected]>
--
Sun Microsystems GmbH Stefan Baltzer
Nagelsweg 55 Quality Assurance Engineer
D-20097 Hamburg Phone: (+49 40)23646 625
http://www.sun.de mailto:[email protected]
Sitz der Gesellschaft: Sun Microsystems GmbH
Sonnenallee 1, D-85551 Kirchheim-Heimstetten
Amtsgericht Muenchen: HRB 161028
Geschäftsführer: Thomas Schröder, Wolfgang Engels, Dr. Roland Bömer
Vorsitzender des Aufsichtsrates: Martin Häring
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
