Hi all,
as Joost suggested, we should collect some ToDo's (or things we feel we
should work on) for the qa project. I've said, I'd come up with my ideas
and I'm late :-(
anyway .. the following items come to my mind and I hope other would
join me and complete the list. Please don't answer yet, how to proceed
with the single tasks, as we cannot do all things at once (and esp. we
cannot handle them all within one mail thread)
First some "short term issues" - things, that are well focused and could
be worked on within the next weeks:
- integration of smoketests into the TCM
Sophie has started a thread about that
(http://qa.openoffice.org/servlets/BrowseList?list=dev&by=thread&from=947615)
What we would need, are people to work with current Smoke Tests and TCM
and go on and integrate them. ATM I have no idea, who of the QA project
is working with TCM. I only know about several native lang projects.
- general review of Test Cases
Jeongkyu Kim made some suggestions. I'm shure, there ar other test
cases, that are unclear or maybe not up-to-date. This job could be
integrated with the first Item
- Review of the online help
ATM, people at least at the francophone and germanophone projects are
reviewing the localized help content, as the translation is (friendly
said) in some cases poor. During this process, problems with english
help have been found as well. Maybe we should put some more work on this.
-release testing
It's somewhat unclear, what the QA project's (or - sorry for the wording
- qa communitie's) role during release testing is. It's clear for
localizations, but not that clear for the english (base) release. We
should define, what has to be done by the qa project (if anthing has to
be done) before a release.
I've sent a agenda item to the CC for clarification of the release
process in general. I think, QA should play a role within that process
.. let's see, what it would look like.
Some more general issues, that need improvement:
- Communication
Mailinglists have become rather silent here at the project. I don't want
to "spam" the list ;-) But we could talk about our work (just as
Christian does from time to time) and ask about triky issues or things
we are unsatisfied with.
-Communication
Beside the lists, we have other means of communication. There is a IRC
channel set up for the OOo qa project and it's *very* silent.
So .. people who work on issues or do tests .. please join the channel,
ask and give answer. The more people are there, the easier it is to
resolve your problem. (And we get the feeling, that there are people
working on issues .. sometimes this seems to get lost when only focusing
on issuezilla.)
IRC Server is Freenode (irc.freenode.net), channel name is #ooonlc .
-Communication
(You get, what I'm trying to say? ;-) )
Members of the QA project cannot read all OOo-lists. So important
information should be forwarded to the QA lists. Most important is
release to me (when do we have new releases to test, release engineering
often asks for help about unconfirmed issues, release engineering should
be informed about stoppers). But forwarding info from user / developer
and discuss lists might be important as well.
BTW - this seems to work, but could be improved.
- website and clear / easy information
I'm not quite shure about that, as I'm member of the project for about
three years now. So to me many things are obvious. But I feel,
information (at our website) could be improved. Esp. new members are
welcome to give feedback about this.
Ok .. enough for the moment. Looking forward reading your comments.
André
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
