https://bugs.freedesktop.org/show_bug.cgi?id=54862
--- Comment #15 from Michael Pappas <[email protected]> --- First, please let me say that I was overenjoyed to read such your comments; clarity and kindness especially striking to me! Thank you! (In reply to comment #13) > 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. Fully understood, I've been employed in open source on and off for the last 12+ years. My comment above was more of a curious nature that is, how come there haven't been a ton of reports about this considering the (IMHO impact). > By the way: these large numbers of bugs do not mean that LibreOffice is a > buggy project with decreasing quality. More complexity brings more bugs and regressions. Trust me, I wouldn't deploy Libreoffice in my organization and I would neither evangelize use of it at hopes, if I *remotely* thought it was unfit for the purpose. > This is why I can just ask you (sorry again!): please be patient. No problem with that! > 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!) Will keep that in mind, thank you. > 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. Thanks again. What *I* can do is search around, find possible similarities, propose/close possible duplicates and basically do whatever it is needed to provide concentrated information for the developer in a *single* place. > 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! Thank YOU, for your kind words and time and effort for a non-profit project! :) -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
