https://bugs.freedesktop.org/show_bug.cgi?id=54862
Roman Eisele <b...@eikota.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |b...@eikota.de
Keywords| |regression
--- Comment #13 from Roman Eisele <b...@eikota.de> ---
Dear Michael Pappas,
thank you very much for your bug report!
(In reply to comment #9)
> It's puzzling to see that this bug has been not been assigned to someone
> yet. Its impact is rather large, especially on organizations with a large
> number of documents in Word format.
I am sorry to say so, but please be patient. LibreOffice is a large project,
and we have limited resources both in development and in QA, so we can’t
process even important bugs as fast as we would like to do.
To adumbrate the dimensions, let me quote some numbers: Right now, there are
3821 NEW/REOPENED/ASSIGNED bugs, i.e. bugs which are confirmed, but not yet
fixed. Additionally, there are 1380 UNCONFIRMED bugs, waiting for confirmation
and moderation by the QA team (which completely consists of volunteers like
me). 645 bugs are in NEEDINFO status, i.e., we are waiting for the users to
respond to necessary questions (they often don’t answer, or only after a long
delay).
But this does not mean that there is no progress. Not less than 7313 bugs are
already RESOLVED/VERIFIED/CLOSED, i.e. have been fixed or processed completely.
For a FLOSS project which consists of mere volunteers, this is IMHO an
impressive result.
By the way: these large numbers of bugs do not mean that LibreOffice is a buggy
project with decreasing quality. Many (most?) of these bugs have been inherited
from OpenOffice.org or even from StarOffice, and we have already fixed a good
part of these old bugs, so that the quality of the software is increasing. But
it is unavoidable that sometimes -- like in this case -- there are also new
bugs introduced while implementing new or improving existing features. That’s a
pitty, but it just happens in every complex software project.
This is why I can just ask you (sorry again!): please be patient.
> No offense here, I know that is a for-free collaborative project. Perhaps
> there are other bugs related to this one, and work is being done for them
> (ergo for this one as well)?
Yes, that is true. It is very probable that the present bug is related or even
identical to some other bug which is already worked on, and that therefore the
fix of that other bug will fix the present issue, too.
If I may add two additional hints:
1) This bug report is about a feature (merged table cells in .doc files?!)
which worked in LibreOffice 3.5 but is broken in LibreOffic 3.6. Therefore it
is what we call a “regression”. In cases like this, you can increase the
likelihood that you report will get noticed early when you add the keyword
“regression” (without the quotes) to the field “Keywords”. (But please do this
only if you are sure that there is a regression!)
2) Our current workflow is (in most cases) as following:
If you report a bug, it will first be reviewed by some QA volunteer(s), who
checks for reproducibility, completeness, probable duplicates etc. Then the QA
volunteer will CC some developer(s) who work in the area of the bug. As soon as
one of these developers finds time, he will check the bug and, if he can handle
it, assign it to himself, and fix it.
This means that it is very important that a bug will catch the eyes of a QA
volunteer, and that this “bug wrangler” (as we call it) can understand and
reproduce the issue easily. Now the present bug has a general summary
(“Formatting problems in Word … files”) which makes it look like a general
report about unspecified (and many) problems. But general reports about many
problems at once are very hard to handle (we need to identify the single issues
first and then to separate them), and therefore bug reports which look like
such general reports are not the favorite bug reports for us QA volunteers ;-)
In short words: Your report is a good one, it is about a specific problem, and
it is well documented with screenshots. The only problem is that the
description of the specific problem comes at the end, and does not catch
everybody’s eyes at once. So you can increase the likelihood that a bug report
like this one will get reproduced soon if you give it a precise summary,
something like “FORMATTING: Merged table cells from .doc file appear not merged
in LibO (Regression)” or so.
Thank you again!
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Libreoffice-bugs mailing list
Libreoffice-bugs@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
