Salut Charles,
I'm going to try:
Currently the quality of experience of OOo on Linux differs greatly
with other platforms such as Windows and often disparities exist also
among Linux distributions.
On Linux, many versions of OOo are actually not considered to be
upstream (binaries coming straight out of www.openoffice.org) but our
source code compiled with the ooo-build system with a varying number
patches coming from Novell, Debian or sometimes the distribution
itself.
Bug reports are filed in several bug trackers with some redundancy and
some loss of information at the same time, with nobody having a clear
vision of what bugs exist in general. Bug trackers work as silos.
A set of solutions has been proposed in order to give to the upstream
bug tracker (OOo) a global visibility on these bugs, by creating one or
several aliases linking to existing bugtrackers for other OOo branches
and in one case to gradually merge the Go-OO IZ into the upstream one
as to pool resources and gain a global visibility on bugs and patches.
I'm not convinced that it's a good idea to have bug reports for builds
of different build providers (including diferent patch/feature levels)
mixed within one bug tracking system. If you need to classify such bug
reports as QA engineer then it often takes too much time to identify the
origin of a bug reported. In such a case it's likely that you/I will
resolve an issue as either invalid or not reproducible/worksforme.
Kind regards, Joost
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
