On Wed, 19 May 2010 14:20:57 +0200 Thorsten Behrens <t...@openoffice.org> wrote:
> > I know the users of OOo on Linux are in conflict. They do not know, > > which OOo they get. Each Linux derivative brings an own build of OOo > > and all of them have different qualities and feature sets. So the > > problem can be solved by using vanilla OOo for all of them. But as > > I know this isn't wanted by the Linux distros. > > > I'm confident it's also not wanted by most of the users - as it > would mean slower start, worse system integration, require manual > update & upgrade handling alien to the built-in one, etc etc. > > Please, let's for once accept the setup of the Linux ecosystem as a > given, and make the best out of the circumstances - which, I > believe, the Charles & Kendy proposal represents. Hi Thorsten, Hi Thorsten, reading the whole thread, I think you are both wrong ;). If somebody builds OpenOffice.org from vanilla source and find a bug in that, that is an valid issue for OpenOffice.org. Even if the bug does not show up in the binaries released officially by Hamburg RelEng, either because of a different configuration or simply by luck or whatever other reason, it is still a bug of the product -- because one of the unique selling points of OpenOffice.org is that it is opensource and so the source is as much part of the product as the binaries. On the other hand, go-oo is heavily patched and not simply a build with a different configuration, thus making it effectively a fork. This is exactly the reason that makes using a common issue tracker problematic: they are different products. All in all, this just screams for distributed bug tracking that allows easy migration of issues between trackers. And although there are efforts like http://bugseverywhere.org and others it seems that a simple to use and stable distributed issue tracker is still years away ... Best Regards, Bjoern --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@qa.openoffice.org For additional commands, e-mail: dev-h...@qa.openoffice.org
