You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by "David C. Rankin" <dr...@suddenlinkmail.com> on 2011/11/09 06:21:03 UTC

Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Guys,

   I apologize if this has been asked and answered, but over the past year I 
have filed several bugs against Libre which would also apply to OO 3.4. How do 
you want to handle these types of issues? Do you review the Libre tracker at 
freedesktop.org or do duplicates bugs need to be opened in the apache tracker?

   I presume you won't want duplicates filed, but is there some mechanism in 
place to make sure those bugs don't slip through the cracks and plague OO 3.4 
the way they have Libre 3.4? May also be worth a note on the 
http://incubator.apache.org/projects/openofficeorg.html page or the 
https://issues.apache.org/ooo/ page. Thanks.

-- 
David C. Rankin, J.D.,P.E.

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Rob Weir wrote on Wed, Nov 09, 2011 at 12:49:56 -0500:
> On Wed, Nov 9, 2011 at 11:12 AM, Pedro Giffuni <pf...@apache.org> wrote:
> > Hello David;
> >
> > If you find a bug in OpenOffice.org file it directly
> > on Apache's bugzilla. Duplicate bug reports are fine,
> > they really are.
> >
> > So far I am the only one in the business of actually
> > committing fixes to issues, so trust me and ignore
> > completely what Rob suggested. I will act with extreme
> > prejudice ignoring any bug report linked to libreoffice
> > on the principle that such contributions or the resulting
> > followups are not made under a compatible license. I won't
> > even look at them.
> >
> 
> Do you really think the facts expressed in a bug report are covered by
> a license?  I'm not talking about patches, but the facts of "Do X, Y
> and Z and Calc crashes?".   If you think that, then I think you are
> mistaken.

I wonder if there's a room for shared bug tracking --- i.e., people
enter a bug once, and then the fix is tracked N times, once for every
set of incompatible licenses the fix is developed under.

(initially N=2)

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Rob Weir <ro...@apache.org>.
On Wed, Nov 9, 2011 at 11:12 AM, Pedro Giffuni <pf...@apache.org> wrote:
> Hello David;
>
> If you find a bug in OpenOffice.org file it directly
> on Apache's bugzilla. Duplicate bug reports are fine,
> they really are.
>
> So far I am the only one in the business of actually
> committing fixes to issues, so trust me and ignore
> completely what Rob suggested. I will act with extreme
> prejudice ignoring any bug report linked to libreoffice
> on the principle that such contributions or the resulting
> followups are not made under a compatible license. I won't
> even look at them.
>

Do you really think the facts expressed in a bug report are covered by
a license?  I'm not talking about patches, but the facts of "Do X, Y
and Z and Calc crashes?".   If you think that, then I think you are
mistaken.

-Rob

> best regards,
>
> Pedro.
>
> --- On Wed, 11/9/11, Rob Weir <ro...@apache.org> wrote:
> ...
>> On Wed, Nov 9, 2011 at 12:21 AM,
>> David C. Rankin
>> <dr...@suddenlinkmail.com>
>> wrote:
>> > Guys,
>> >
>> >  I apologize if this has been asked and answered, but
>> over the past year I
>> > have filed several bugs against Libre which would also
>> apply to OO 3.4. How
>> > do you want to handle these types of issues? Do you
>> review the Libre tracker
>> > at freedesktop.org or do duplicates bugs need to be
>> opened in the apache
>> > tracker?
>> >
>>
>> Hi David, thanks for the great question.  I don't
>> think I've seen this
>> question come up before.
>>
>> Currently there is no automatic exchange of bug reports
>> between the
>> two projects.  I don't think that would make sense in
>> general.  From
>> what I've seen there are many bugs in LO that do not exist
>> in OOo, and
>> presumably when we put out Apache releases we'll have bugs
>> that don't
>> exist in LO.  But certainly there will be defects that
>> exist in both
>> products.  And where we know that it will make sense
>> to share the
>> reports.
>>
>> Probably the easiest solution is, when you believe the
>> defect exists
>> in OOo as well, to enter a new defect in the AOOo Bugzilla,
>> with a
>> link to the LO defect. And then add a comment to the LO
>> defect
>> pointing to the AOOo defect report.  No need to
>> duplicate the content,
>> but it would be useful to cross-link the defect reports.
>> That way it
>> will be easier for LO to find and grab our patches when we
>> fix an
>> issue.
>>
>> >  I presume you won't want duplicates filed, but is
>> there some mechanism in
>> > place to make sure those bugs don't slip through the
>> cracks and plague OO
>> > 3.4 the way they have Libre 3.4? May also be worth a
>> note on the
>> > http://incubator.apache.org/projects/openofficeorg.html
>> page or the
>> > https://issues.apache.org/ooo/ page. Thanks.
>> >
>>
>> Let's see if there are any better ideas for how to track
>> these
>> cross-product defects, and then we can document the
>> consensus
>> recommendations, on the website (hopefully also at the LO
>> website as
>> well).
>>
>> Regards,
>>
>> -Rob
>>
>> > --
>> > David C. Rankin, J.D.,P.E.
>> >
>>
>

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Pedro Giffuni <pf...@apache.org>.
Thanks;

--- On Wed, 11/9/11, David C. Rankin <dr...@suddenlinkmail.com> wrote:

> 
> Hi Pedro, Rob,
> 
>   Always good to get the scoop 'straight from the
> horses mouth' so to speak :) There are a couple old OOO bugs
> that would be nice to get cleaned up. Specifically:
> 
> #Issue: 81402 Tab Stops
> duplicate of: 21292
> http://www.openoffice.org/issues/show_bug.cgi?id=21292
> 

The new link for that is now this:

https://issues.apache.org/ooo/show_bug.cgi?id=21292

I added myself to this issue in case a fix for this
appears.

Sorry that I am busy with the FreeBSD and OS/2 ports
at the moment :).

Pedro.


Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by "David C. Rankin" <dr...@suddenlinkmail.com>.
On 11/09/2011 10:12 AM, Pedro Giffuni wrote:
> Hello David;
>
> If you find a bug in OpenOffice.org file it directly
> on Apache's bugzilla. Duplicate bug reports are fine,
> they really are.
>
> So far I am the only one in the business of actually
> committing fixes to issues, so trust me and ignore
> completely what Rob suggested. I will act with extreme
> prejudice ignoring any bug report linked to libreoffice
> on the principle that such contributions or the resulting
> followups are not made under a compatible license. I won't
> even look at them.
>
> best regards,
>
> Pedro.

Hi Pedro, Rob,

   Always good to get the scoop 'straight from the horses mouth' so to speak :) 
There are a couple old OOO bugs that would be nice to get cleaned up. Specifically:

#Issue: 81402 Tab Stops
duplicate of: 21292
http://www.openoffice.org/issues/show_bug.cgi?id=21292

If we can get default tabs at .50 in the english release instead of .49 in., 
that would make life much better. Bug has only been around for about 7 years or 
so :)

   There is also some horrible default behavior in numbered paragraphs and 
copy/paste that should either be configurable as options or reworked:

copy/paste default

   https://bugs.freedesktop.org/show_bug.cgi?id=40558

Numbered Paragraph Bug

   https://bugs.freedesktop.org/show_bug.cgi?id=40560

   I have a couple more floating around I'll have to look up and get them 
registered with the AOO tracker. I should have time to enter them later this 
week or weekend. I'll also have to look up my earlier OOO bugs and revisit them 
as well.

   OOO 3.3 was in reasonable shape. It has some small, but very real annoyances, 
that with a little effort could really make the package shine.

   I use OOO exclusively in my office and I probably use an office suite to a 
much larger extent and degree than 99% of the normal Linux users (I'm a lawyer, 
documents and spreadsheets are my life) I'm also an engineer and Linux nut so I 
have a rather strange set of skills I bring to the table.

   I look forward to the AOO 3.4 release. The 3.X releases have been a bit rocky 
to date. (2.4.x was fantastic)

   Always remember -- make the core pieces of each app logical, efficient and 
bulletproof and always think of backwards compatibility (for the decade worth of 
prior documents that need seamless reproduction), then -- and only then -- worry 
about the gee-whiz new bells and whistles of the package.

   The core of a word processor, spreadsheet and presentation package should 
remain stable and without radical change in function or interface. New stuff 
should be added as options with user configurable options available to control 
new behavior. ( Remember - a new 'feature' is a 'bug' if you can't turn it off )

   Thanks again for your tireless work to date and I look forward to working 
with AOO in the future.

-- 
David C. Rankin, J.D.,P.E.

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Andrea Pescetti <pe...@openoffice.org>.
On 09/11/2011 Pedro Giffuni wrote:
> On the long run I think LO and
> AOOo will keep diverging more and more and the number
> of shared bugs will eventually vanish.

It might be, but in recent months I actually did cross-link bugs from 
the OpenOffice.org Bugzilla to the LibreOffice bug tracker and vice 
versa, a few times.

Since many users of OpenOffice.org are not technical and might be unable 
to properly describe a bug, having a bug properly triaged on the 
LibreOffice tracker will save time for the OpenOffice.org developers 
(and the same holds the other way round, of course, the only difference 
being license compatibility of patches, but this is another stage; I'm 
only considering bug triaging here).

Regards,
   Andrea.

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Pedro Giffuni <pf...@apache.org>.
Hi again Regina:

--- On Wed, 11/9/11, Pedro Giffuni <pf...@apache.org> wrote:
...
> being applied here: don't expect committers to do
> everything, we have a life too!
> 

I should've added a wink ( ;) ) here, as I didn't
mean to be rude. I know perfectly well that you
go very far in your testing activities and you are
a great contributor here. 

Email is not a very good means of communication so
by all means don't let my bad day get in your way
and keep doing the great contributions that you do!

best regards,

Pedro.

> 
> --- On Wed, 11/9/11, Regina Henschel <rb...@t-online.de>
> wrote:
> 
> > 
> > I do not understand, why you will ignore solutions
> found in
> > LibreOffice. For example bug https://issues.apache.org/ooo/show_bug.cgi?id=115922
> > has a solution in https://bugs.freedesktop.org/show_bug.cgi?id=32872.
> Why
> > do you will ignore it?
> > (Actually it is a simple typo
> FontWorkAlignmentController
> > -> FontworkAlignmentController)
> > 
> > Even if you can not take the patch as it is, the bug
> report
> > in LibreOffice might tell you the reason of the
> problem and
> > it might contain valuable comments and test
> documents.
> > 
> > Kind regards
> > Regina
> > 
> 

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Pedro Giffuni <pf...@apache.org>.
I will certainly ignore it.

Patches expressly submitted through our bugzilla are
or our mailing list safely covered by AL2 section 5.

While I *could* look at the issue and ask for permission
to apply the the fix, or I *could* implement alternative
fixes, I choose to work with our own community on issues
that have been tested and proved here (and we are not
running short on those). On the long run I think LO and
AOOo will keep diverging more and more and the number
of shared bugs will eventually vanish.

This is my own position though. I don't pretend this
to apply to others and certainly issue submitters can
do their part of the homework when they submit issues
by verifying if it has been solved elsewhere, what
caused it and even if the author is OK with the patch
being applied here: don't expect committers to do
everything, we have a life too!

best regards,

Pedro.

--- On Wed, 11/9/11, Regina Henschel <rb...@t-online.de> wrote:

> 
> I do not understand, why you will ignore solutions found in
> LibreOffice. For example bug https://issues.apache.org/ooo/show_bug.cgi?id=115922
> has a solution in https://bugs.freedesktop.org/show_bug.cgi?id=32872. Why
> do you will ignore it?
> (Actually it is a simple typo FontWorkAlignmentController
> -> FontworkAlignmentController)
> 
> Even if you can not take the patch as it is, the bug report
> in LibreOffice might tell you the reason of the problem and
> it might contain valuable comments and test documents.
> 
> Kind regards
> Regina
> 

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Regina Henschel <rb...@t-online.de>.
Hi Pedro,

Pedro Giffuni schrieb:
> Hello David;
>
> If you find a bug in OpenOffice.org file it directly
> on Apache's bugzilla. Duplicate bug reports are fine,
> they really are.
>
> So far I am the only one in the business of actually
> committing fixes to issues, so trust me and ignore
> completely what Rob suggested. I will act with extreme
> prejudice ignoring any bug report linked to libreoffice
> on the principle that such contributions or the resulting
> followups are not made under a compatible license. I won't
> even look at them.

I do not understand, why you will ignore solutions found in LibreOffice. 
For example bug https://issues.apache.org/ooo/show_bug.cgi?id=115922 has 
a solution in https://bugs.freedesktop.org/show_bug.cgi?id=32872. Why do 
you will ignore it?
(Actually it is a simple typo FontWorkAlignmentController -> 
FontworkAlignmentController)

Even if you can not take the patch as it is, the bug report in 
LibreOffice might tell you the reason of the problem and it might 
contain valuable comments and test documents.

Kind regards
Regina

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Pedro Giffuni <pf...@apache.org>.
Hello David;

If you find a bug in OpenOffice.org file it directly
on Apache's bugzilla. Duplicate bug reports are fine,
they really are.

So far I am the only one in the business of actually
committing fixes to issues, so trust me and ignore
completely what Rob suggested. I will act with extreme
prejudice ignoring any bug report linked to libreoffice
on the principle that such contributions or the resulting
followups are not made under a compatible license. I won't
even look at them. 

best regards,

Pedro.

--- On Wed, 11/9/11, Rob Weir <ro...@apache.org> wrote:
...
> On Wed, Nov 9, 2011 at 12:21 AM,
> David C. Rankin
> <dr...@suddenlinkmail.com>
> wrote:
> > Guys,
> >
> >  I apologize if this has been asked and answered, but
> over the past year I
> > have filed several bugs against Libre which would also
> apply to OO 3.4. How
> > do you want to handle these types of issues? Do you
> review the Libre tracker
> > at freedesktop.org or do duplicates bugs need to be
> opened in the apache
> > tracker?
> >
> 
> Hi David, thanks for the great question.  I don't
> think I've seen this
> question come up before.
> 
> Currently there is no automatic exchange of bug reports
> between the
> two projects.  I don't think that would make sense in
> general.  From
> what I've seen there are many bugs in LO that do not exist
> in OOo, and
> presumably when we put out Apache releases we'll have bugs
> that don't
> exist in LO.  But certainly there will be defects that
> exist in both
> products.  And where we know that it will make sense
> to share the
> reports.
> 
> Probably the easiest solution is, when you believe the
> defect exists
> in OOo as well, to enter a new defect in the AOOo Bugzilla,
> with a
> link to the LO defect. And then add a comment to the LO
> defect
> pointing to the AOOo defect report.  No need to
> duplicate the content,
> but it would be useful to cross-link the defect reports.
> That way it
> will be easier for LO to find and grab our patches when we
> fix an
> issue.
> 
> >  I presume you won't want duplicates filed, but is
> there some mechanism in
> > place to make sure those bugs don't slip through the
> cracks and plague OO
> > 3.4 the way they have Libre 3.4? May also be worth a
> note on the
> > http://incubator.apache.org/projects/openofficeorg.html
> page or the
> > https://issues.apache.org/ooo/ page. Thanks.
> >
> 
> Let's see if there are any better ideas for how to track
> these
> cross-product defects, and then we can document the
> consensus
> recommendations, on the website (hopefully also at the LO
> website as
> well).
> 
> Regards,
> 
> -Rob
> 
> > --
> > David C. Rankin, J.D.,P.E.
> >
> 

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Rob Weir <ro...@apache.org>.
On Wed, Nov 9, 2011 at 12:21 AM, David C. Rankin
<dr...@suddenlinkmail.com> wrote:
> Guys,
>
>  I apologize if this has been asked and answered, but over the past year I
> have filed several bugs against Libre which would also apply to OO 3.4. How
> do you want to handle these types of issues? Do you review the Libre tracker
> at freedesktop.org or do duplicates bugs need to be opened in the apache
> tracker?
>

Hi David, thanks for the great question.  I don't think I've seen this
question come up before.

Currently there is no automatic exchange of bug reports between the
two projects.  I don't think that would make sense in general.  From
what I've seen there are many bugs in LO that do not exist in OOo, and
presumably when we put out Apache releases we'll have bugs that don't
exist in LO.  But certainly there will be defects that exist in both
products.  And where we know that it will make sense to share the
reports.

Probably the easiest solution is, when you believe the defect exists
in OOo as well, to enter a new defect in the AOOo Bugzilla, with a
link to the LO defect. And then add a comment to the LO defect
pointing to the AOOo defect report.  No need to duplicate the content,
but it would be useful to cross-link the defect reports. That way it
will be easier for LO to find and grab our patches when we fix an
issue.

>  I presume you won't want duplicates filed, but is there some mechanism in
> place to make sure those bugs don't slip through the cracks and plague OO
> 3.4 the way they have Libre 3.4? May also be worth a note on the
> http://incubator.apache.org/projects/openofficeorg.html page or the
> https://issues.apache.org/ooo/ page. Thanks.
>

Let's see if there are any better ideas for how to track these
cross-product defects, and then we can document the consensus
recommendations, on the website (hopefully also at the LO website as
well).

Regards,

-Rob

> --
> David C. Rankin, J.D.,P.E.
>

Re: Do recent bugs filed against Libre 3.4 need to be refiled with apache tracker?

Posted by Shane Curcuru <as...@shanecurcuru.org>.
Thank you, David, for looking to ensure that issues that might pertain 
to multiple projects are reported appropriately to each project.  We 
definitely appreciate the extra effort from our users!

Personally, I think it would be good to submit full independent bugs to 
each project's issue tracker.  Since the active development communities 
are notably different, this would make it easier for AOOo and LO 
developers to work on fixes in their respective projects.  But that's 
just my suggestion.

Thanks!
- Shane

On 2011-11-08 9:21 PM, David C. Rankin wrote:
> Guys,
>
> I apologize if this has been asked and answered, but over the past year
> I have filed several bugs against Libre which would also apply to OO
> 3.4. How do you want to handle these types of issues? Do you review the
> Libre tracker at freedesktop.org or do duplicates bugs need to be opened
> in the apache tracker?
>
> I presume you won't want duplicates filed, but is there some mechanism
> in place to make sure those bugs don't slip through the cracks and
> plague OO 3.4 the way they have Libre 3.4? May also be worth a note on
> the http://incubator.apache.org/projects/openofficeorg.html page or the
> https://issues.apache.org/ooo/ page. Thanks.
>