Hi Kendy,
On 05/20/10 00:45, Jan Holesovsky wrote:
Hi Thorsten,
On Wednesday 19 May 2010, Thorsten Ziehm wrote:
I couldn't accept (as a member of the QA project on OOo) that we
have to spend resources of the OOo project to making QA* in OOo
derivatives which doesn't spend resources for this project and
which doesn't contribute their code.
Sure, understood, but we are talking about go-oo; go-oo developers contribute
code up-stream.
Perhaps I misunderstood the releases of go-oo. In the following blog
you can find links, what is/isn't contributed to OOo. As you can see
the products are differ in parts a lot.
http://lizards.opensuse.org/2010/05/17/openoffice_org-3_2_1_1/
The resources will be missing
for making Quality Assurance for the OOo (vanilla) and will lead
to a worser quality of all OOo derivatives. This isn't acceptable
for me, perhaps for you too.
I am afraid I did not explain my proposal well enough, sorry for that :-(
Currently, when you, as a QA person, find out that a bug is not present in the
up-stream version, you just close it as invalid, which helps no-one - the
reporter is just confused, you have to spend time explaining why it is
invalid, and go-oo maintainers do not learn about that bug, which - as
Charles and Mechtilde pointed out - might in the end affect the perception of
the entire OOo.
How often the QA person should go in contact with the bug reporter to
get the feedback that is a bug in Ubuntu or any other distro version?
This is the time which costs resources.
I would like to ask you to try the alias solution I proposed. I have just
created a go_oo_b...@openoffice.org user; if you find out that a bug is
invalid in up-stream, but the reporter talks about a particular Linux distro
(openSUSE, Debian, Ubuntu, ...), just reassign it to
go_oo_b...@openoffice.org, instead of setting it as 'invalid'. The
notification will go to our mailing list (ooo-bu...@lists.freedesktop.org at
the moment, and I asked for a dedicated one), and no other work for you - we
will take care of the rest.
Do you know, how many issues we talk about currently? Near to 600 issuer
are set to invalid or worksforme since begin of 2010. And I heard by
some of my QA engineers, that these issues are often for OOo versions of
other distros.
If you want to get a feeling, what the situation is. Please query for
all invalid issues from the past month. Evaluate them and evaluate if
these issues are in 'not-vanilla' OOo versions are only.
Do you think it might work for you, please?
If a process of handling such issues (I wrote about it some mails ago)
exists and the alias aren't a black hole where nothing happen, than it
might work. But it still costs resources in the mother-project OOo. And
this I want to avoid.
Thorsten
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org
For additional commands, e-mail: dev-h...@qa.openoffice.org
