https://bugs.documentfoundation.org/show_bug.cgi?id=34467
--- Comment #43 from Joel Madero <[email protected]> --- (In reply to Wolfgang Jäger from comment #42) > > I will not report new details whether there may be some or not. As long as > the bug is stll NEW in its sixth year of life despite the many confirming > comments and not officially recognised nothing will happen, I am afraid. > > Can someone explain this to me? The explanation is simple. This is a volunteer project, for a bug to get fixed a volunteer has to find it interesting. The options are always the same: 1) Fix it yourself - code is readily available; 2) Find a friend/family/colleague to fix it; 3) Pay for a fix; 4) Wait for a volunteer to tackle it. Most of us fall into category 4 (10's of millions of users, a few dozen really active developers). We have a few thousand open issues, plus of course volunteer developers are doing cool things that they find interesting. So yes, sometimes a bug can sit "confirmed" (NEW) for a long time - this is the world of open source. -- You are receiving this mail because: You are the assignee for the bug.
_______________________________________________ Libreoffice-bugs mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/libreoffice-bugs
