Re: Bugs already fixed in LibreOffice
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
Re: Bugs already fixed in LibreOffice
On Sat, Mar 29, 2014 at 11:43 AM, Pedro Lino wrote: > Hi all > > I have reported many bugs and some have already been solved in LibreOffice. > I'm wondering if it makes sense to report them *again* to the Apache > bugzilla... > 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. > However, since the LibreOffice license is not compatible with Apache, does > this mean that the solution used by LibreOffice can no longer be used? > > E.g. if the solution for problem X is 1+1 then Apache must find a > workaround to reach the same result (something like (2*(1+1))/2 )??? > > What if there is a *single* solution to a problem (e.g. there should be a > comma where there is a semi comma by mistake)? Are the Apache developers > forbidden to use the same solution because someone already submitted a > patch to LibreOffice that does this? > 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. Regards, -Rob > Cheers, > Pedro - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Re: Bugs already fixed in LibreOffice
On Sat, Mar 29, 2014, at 18:43, Pedro Lino wrote: > Hi all > > I have reported many bugs and some have already been solved in LibreOffice. > I'm wondering if it makes sense to report them *again* to the Apache > bugzilla... Yes - these are different products. > > However, since the LibreOffice license is not compatible with Apache, does > this mean that the solution used by LibreOffice can no longer be used? AFAIK - no. > > E.g. if the solution for problem X is 1+1 then Apache must find a > workaround to reach the same result (something like (2*(1+1))/2 )??? > > What if there is a *single* solution to a problem (e.g. there should be a > comma where there is a semi comma by mistake)? Are the Apache developers > forbidden to use the same solution because someone already submitted a > patch to LibreOffice that does this? To my understanding there are many ways to fix a bug / implement an enhancement. > > Cheers, > Pedro - To unsubscribe, e-mail: qa-unsubscr...@openoffice.apache.org For additional commands, e-mail: qa-h...@openoffice.apache.org
Bugs already fixed in LibreOffice
Hi all I have reported many bugs and some have already been solved in LibreOffice. I'm wondering if it makes sense to report them *again* to the Apache bugzilla... However, since the LibreOffice license is not compatible with Apache, does this mean that the solution used by LibreOffice can no longer be used? E.g. if the solution for problem X is 1+1 then Apache must find a workaround to reach the same result (something like (2*(1+1))/2 )??? What if there is a *single* solution to a problem (e.g. there should be a comma where there is a semi comma by mistake)? Are the Apache developers forbidden to use the same solution because someone already submitted a patch to LibreOffice that does this? Cheers, Pedro
Re: AOO 4.1 Full Regression Test Starts! Call for volunteers!
Yuzhen Fan wrote: > We have released AOO 4.1 Beta sucessfully ... the next > test stage is FPR (full regression test) ... please send a note to the QA mailing list (qa@openoffice.apache.org). If > you have a > Testlink account[2] send your ID as well as what platform you can help > test(if you haven't a Testlink account, you can register one). You should > also get installation sets from trunk [3] and report issues in Bugzilla > [4]. You may want to see detail instructions in Test Guidence [5]. > > Count me in: TestLink ID: talchu, Mac OS X 10.9. Note: I'm new at this, and would like to focus in BiDi/RTL, if possible, since I found major bugs in this area, in the past. > [1] > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Release+Planning > [2] http://aootesting.adfinis-sygroup.org/index.php > [3] http://ci.apache.org/projects/openoffice/ > [4] https://issues.apache.org/ooo/ > [5] > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.1+Full+Regression+Test+Guidance
