Hello Charles,
welcome to the QA team. I've granted 'canconfirm' privileges to your
account.
Please take some minutes to read
http://qa.openoffice.org/helping.html
http://qa.openoffice.org/issue_handling/index.html
http://qa.openoffice.org/priorities.html
to get an idea about what can be done.
If you're interested into doing some automation then there are two ways:
http://qa.openoffice.org/qatesttool/index.html
That's GUI based automated testing. The scripting language used is some
kind of BASIC dialect.
http://qa.openoffice.org/qadevOOo_doc/index.html
That's API based testing.
If you need help then please ask here within this list.
On the page http://qa.openoffice.org/issuelinks.html you find some links
containing queries for unconfirmed issues which need triage.
BTW, I have some questions.
1- Is there somewhere a list of keywords for issues?
http://www.openoffice.org/issues/describekeywords.cgi
2- How to determine the target of an issue?
Usually those who implement a bugfix or a feature determine the target
of an issue. Please don't touch the target field if you don't have
someone who does the implementation.
3- I noticed some of my issues are assigned to 'requirements'. What is
that?
The (virtual) user "requirements" is someone (mainly bh) who cares about
the planning of the implementation of features. In this case Bettina
(bh) preselects rfe/feature issues and defines targets.
4- What are 'Glow 0.2', 'CEE ...', and 'OOo PleaseHelp' targets?
Glow was the development name of a groupware client
http://groupware.openoffice.org/glow/
It's been inactive since a longer time. "CEE" I believe is the
abreviation of the name of the website infrastructure software. The "OOo
PleaseHelp" can be set if the responsible developer doesn't know how to
proceed further and asks for help. In this case there's no target
defined for that issue where it's planned to be fixed.
5- Is it the job of QA or of the developer assigned to the issue to
confirm a new issue?
Confirming issues is mostly the job of QA team members. If a developer
confirms an issue by himself...that's very good...
6- What is the field 'QA contact' for?
That's the person(s) involved into QA'ing and testing a bugfix.
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
