<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [META] - Feature "not implemented on platform X"" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129806#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [META] - Feature "not implemented on platform X"" href="https://bugs.documentfoundation.org/show_bug.cgi?id=129806">bug 129806</a> from <a class="email" href="mailto:olivier.hallot@libreoffice.org" title="Olivier Hallot <olivier.hallot@libreoffice.org>"> Olivier Hallot</a> <pre>The point in adding to the Help is the maintenance work to keep contents precise and updated. Suppose that the issue on WIN/ssh is fixed someday. Who will pick the right Help pages and correct its contents? Or, how to let Help maintainers know the issue is fixed/implemented/whatever? It seems hard to me to traverse Help pages checking for bugs fixed or new features. Very few dev's and QA volunteers care to report changes in the Help, but those who do are my heroes. I wonder if we can implement an extra field in bugzilla bug report to indicate the associated help pages to touch. Either way, it is a hard and time consuming job. Another drawback is more in the marketing side... It looks bad for a product/software to let user know it is broken, even on the weirdest corner case. Better let user discover bugs by him/herself. Some companies publish the "known bugs" list at release time, but that not so often to see nowadays (and very few read it).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>