Hi Rob, all If you know the bug exists in AOO as well, then feel free to report it > in BZ. But it is worth checking, since there are many LO bugs that > never existed in AOO. >
Obviously ;) Here is an example of a bug that exists in OO since 2005(!!!) and still occurs in AOO 4.1.0 Beta (otherwise it wouldn't makes sense to report it...) https://issues.apache.org/ooo/show_bug.cgi?id=59059 As you can see in the latest comment (#11), this is already fixed in LO https://bugs.freedesktop.org/show_bug.cgi?id=43807 > We cannot copy the source code of LO into AOO. But looking at bug > reports and even developer comments on bug reports is fine. So if a > LO bug report says "LO crashes when doing Foo" and a developer later > comments, "Fixed. Issue was that X must be 1+1", then it is fine for > us to confirm the bug exists in AOO and for a developer to try a > similar fix. If there is only a single reasonable solution to a bug > then it would be natural for the bug fixes to be quite similar. But > in general AOO developers should avoid looking at LO source code. > > Also, if there is a 3rd party patch attached to an issue, we could > contact the author of the patch and ask if they agree to make it > available to AOO as well, under the Apache License. We've integrated > several LO patches in this way. > Thank you for the clarification. I'm glad it works that way. It would be absurd for a solution to prevent another product to be fixed as well. Regards, Pedro
