[Libreoffice-qa] Where should users report bugs?

Thomas Hackert thackert at nexgo.de
Wed Nov 6 01:47:54 PST 2013

Hello @gain,
On Dienstag, 5. November 2013 20:35 Robinson Tryon wrote:

> On Tue, Nov 5, 2013 at 9:20 AM, Thomas Hackert <thackert at nexgo.de>
> wrote:
>>>> => What bugs should be reported to our LibreOffice bugtracker?
>>>> => What bugs should be reported to distros?
>> I would say only bugs, that are in our version of LO should go to
>> our bugtracker, but the ones from the distros to their adequate
>> bugtracker ... ;)
> I think that there's general agreement on that front, although
> some people have expressed concern at the time that it might take
> a bug to "bubble up" from a distro's bugtracker and reach us.
> Perhaps we should
> 1) Figure out how many non-distro-specific bugs are reported
> downstream

from all existing different distros and their bugtracker? This would 
mean a lot of work, I think ... :( Except, there would be some kind 
of automatism to collect all the data ... ;)

> 2) Figure out how much longer it takes for them to reach our devs
> than bugs reported in FDO

And how would you do this?

>> Maybe we could close those bugs with a comment á
>> la "This bug is only related to $version of $distro. @reporter:
>> Would you be so kind to report it again at $link?“ or the like
>> ... ;)
> Personally, I'd like to cultivate a relationship with the
> maintainers of LibreOffice in each distro and be able to "give"
> them these bugs. Before we close the bug in FDO, I'd like to
> assign it to that maintainer so that they can open a corresponding
> bug in the distro bugtracker.

I like the idea from your linked LWN article, where "dberkholz" 
commented, that (s)he asks his users for his/her Gentoo package(s) 
to report it upstream, but CC him/her to this bug (see 
http://lwn.net/Articles/423838/), when they are only reproducible 
upstream. And if this could be done the other way (= to report bugs 
downstream, but CC a generic mail address, so it could be tracked by 
our devs/QAs) as well, would be great :) What do you (or others) 
think? Would this be possible? Though it would be a lot of work to 
find the different maintainers on the different distros and ask them 
for permission / their opinion beforehand ... :(

> Do we have a 'downstream' mailing list for distros? It might be
> handy to have something like that... :-)

No idea ... :( But yes, I think, this could be really useful :)

<snipped, as there is another mail related to the feedback page ... 
;) >
>>> If we want distros to receive some/all bugs filed against
>>> distro-provided builds of LibreOffice, then we should think
>>> about the best way to patch-out that menu option so that the
>>> program will send users to the right BTS.
>> Would it not be better, when each distro changes this to their
>> own BTS?
> Oh, certainly. I don't have any recent distro builds of
> LibreOffice to determine if they change the URL -- can you confirm
> this one way or the other?

On my desktop PC, I am only using LO builds from our website. But 
after starting my eeePC 1000H with Debian Testing i386 and the 
installed Germanophone version of LO with Build ID: 410m0 
(Build 3) there, it opens www.libreoffice.org/get-
help/bug/?LOversion... (sorry, I have to type it by hand, as I have 
not configured a LAN here as I am still looking for a good 
HowTo/documentation on how I can configure my network that way, that 
I am just using my ISP's router to exchange files between this two 
devices, but without installing any server stuff on my desktop PC 
... :( ) ... :( I am not sure, if it is already reported to Debian's 
BTS, though ... :(

>> I am not sure, if there is already a feature request in one of
>> the different BTSes though ... :(
> That's a good point re: Feature requests. Hopefully those would
> also "bubble up" to us over time...

/me too ... ;)
Read you

The denunciation of the young is a necessary part of the hygiene of 
older people, and greatly assists in the circulation of the blood.
		-- Logan Pearsall Smith

More information about the Libreoffice-qa mailing list