Hi Charles,
Charles-H. Schulz wrote (20-05-10 16:10)
Le Wed, 19 May 2010 22:59:58 +0200,
Cor Nouws<[email protected]> a écrit :
The discussion went a bit wide sometimes (IMO)
Charles, could you pls help me and write in 2, 3 short sentences what
the goal is, and by what simple means could be started (as concluded
in the discussion).
(Leaving out for the moment the more complex stuff (of various
nature))
Thanks,
Cor
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.
Does it sound better?
Still longgg sentences ;-) but it helps yes; thanks.
Reading a bit through the other posts now, I see one simple step
supported widely: that is
- to use aliases so that down-stream versions can pick up the issues
that are invalid for vanilla OOo,
- where it is expected (Thorsten Ziehm) that Hamburg QA will not
really spend time in finding out which non-vanilla version in involved,
might that be unclear.
Curious how it works out and what possibly grows from of it...
I see Mechtilde cannot wait starting to work with it.
Best,
Cor
--
>> Your office 2010 software: the new OpenOffice.org <<
Cor Nouws
- ideas/remarks for the community council?
- http://wiki.services.openoffice.org/wiki/Community_Council
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
