Hello Kendy, *,
On Thu, May 20, 2010 at 12:45:31AM +0200, Jan Holesovsky wrote:
> 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.
and the developer from other places/distros? Do they not contribute
code upstream ;?
> > 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.
+1
> I am afraid I did not explain my proposal well enough, sorry for
> that :-(
It seems so ... ;)
> 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.
+1
> 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.
I think, this would only be useful, if any distro has its own alias
and therefore a person/team, which gets the mail for this alias,
coordinate its distribution to his/her teammates and the like ...
> Do you think it might work for you, please?
Not sure about ... :( /If/ every distro creates an alias, /if/ the
appropriate team is responsible for these issues ... And then the
team behind one alias should create an workflow between handling
their own BTS/IZ and issues in OOo upstream ... ;) But I am not
sure, how practicable this would be ... :(
Just one other idea: Would it be helpful to set "[$distro]" in front
of the summary line of an issue to filter the issues for $distro?
Just my thoughts in this longish discussion ... ;)
Thomas.
--
An ounce of hypocrisy is worth a pound of ambition.
-- Michael Korda
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org
For additional commands, e-mail: dev-h...@qa.openoffice.org
