Andrew Jensen, 02-05-2007 16:05:
First - there are distributions downloaded from OOo mirrors.

Our OOo.

Second - there are distributions downloaded from ftp.linux.cz

Idem.

Third - OOo distributions from my Linux distributor, Ubuntu

OOo from ooo-build, modified by Debian, modified by Ubuntu.

Fourth - I will be looking at what Novel is now offering.

OOo from ooo-build.

Now, I would of thought that the first two sources should be giving me
pretty much the same thing - but experience has proven that not to
always be the case. I will sometimes run into a problem with OOo from
linux.cz that does not happen in the same version of OOo retrieved
from an OOo mirror, less often this has been reversed.

The translations are different usually, since Pavel uses the community language files (it is the reason for those builds existence).
The language files are updated more frequently than they got into OOo.
The codebase is the same.

Is there a policy, or a recommendation, or opinion, about which
distributions are valid for testing of issues in the OOo tracking
system?

The ones from ooo-build are not valid, the ones from linux.cz and from OOo (of course) are.

What about for opening new issues?

Original -> we
ooo-build -> the packager, that means, novell or ubuntu or debian or redhat or...

Some things are patently obvious - finding a problem with VBA support,
or with the new extension for importing/exporting MS XML file formats
under the Novel distributuion for example rightfully belongs to Novel.

The build you're using is what matters.

An example of what is not so clear to me is this. When I downloaded
the 2.3m_211 file from linux.cz and installed it, it did not install
as OOo-Dev, rather as OpenOffice.org 2.3. It created a new directory
structure for this 2.3 release and then quietly removed all the files
form the OpenOffice.og 2.2 directory tree. The splash screens all say
2.2, but the help screens say 2.3. Do I just not report this to
anyone? If I do report it, do I do so via mailing lists and not the
Issue tracker?

SRC680_m211 is a development package. The ones from linux.cz aren't official, so you could expect things like that. Since it's not any version itself, showing 2.2 splash is not an issue, actually.

All bug reports should be done through Issue Tracker. Of course you can ask here if in doubts.

Anyway, I hope you get the gist of what I am wondering about.

I hope you've got what I've said:
if you've found a bug on original OOo (OOo, linux.cz), file an issue for us. If you've found an issue on ooo-build (from Novell, Ubuntu, Debian, RedHat...) file an issue to the maintainer of the package you've downloaded.

If the issue is with some of the linux.cz packages and does not happen on the official one, you should put it clear on the description and maybe add pj (@ooo) to the CC field ;).


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to