[Libreoffice-qa] Bug Triage: What takes the most time? What slows you down?

Alex Thurgood alex.thurgood at gmail.com
Thu Jul 2 02:11:26 PDT 2015

Le 01/07/2015 15:28, Robinson Tryon a écrit :

Hi Robinson,

> Even if your nick is more active than IZBot in the #libreoffice-qa
> channel, there are only so many bugs that you can triage in an hour.
> I'm interested in hearing what takes the biggest chunk of your time
> during bug triage, so we can see if we can simplify and/or reduce the
> time/energy that we spend on each bug.

Generally, poorly worded initial bug reports. I'm less inclined nowadays
to try and second guess what the user has done (or not done), so tend to
stick them straight to NEEDINFO with questions.

Printing bugs and specific database setups also waste a lot of time.
With printer bugs, if you don't have that printer, very often,
attempting to triage is useless, other than stating that you  can't
reproduce on x,y,z printer which is not the one the user filed the bug

Database bugs are painstaking to reproduce without a sample file
provided by the reporter or else complete instructions on how to set up
their particular scenario, and that only works if one has access to the
particular database server - obviously this is easier with integrated
hsqldb. In a database bug, you need to look at :

server (and version) db  vs. embedded db vs file db;
connector : JDBC / ODBC / native;
table definitions;
query definitions;
report builder version;
Java version.

I only really look at Mac UNCO and db UNCO.

Mac UNCO has been shown to be dependent on OSX version - there are some
bugs I simply can't confirm because I don't see them on OSX 10.10 and
the bugs are reported against earlier versions.


More information about the Libreoffice-qa mailing list