Public Appeal to LibreOffice Source Code Contributors

LibreOffice is among the finest software applications I have ever used, and I deeply appreciate all the contributions that have made it so feature-rich and reliable. However, I have a humble request: please ensure that every contribution is thoroughly tested before it is merged into the codebase.

If anyone is still reading, I would like to share more information for your consideration.

I would like to see an improvement in the testing process for LibreOffice. When a change is made to the source code, it should ideally undergo review and testing by at least two independent testers, followed by approval from a senior developer.

1) Even seemingly minor or trivial changes in the source code can have significant and potentially disruptive effects on the user experience. For example, a shortcut key combination — Ctrl + Shift + C — was assigned to the "Track Changes" function:

https://gerrit.libreoffice.org/c/core/+/65041

This raised concerns: Who approved this change? Who tested and validated it before it was committed?

Many users, including myself, were confused as to why the "Track Changes" feature was suddenly being triggered unexpectedly. The impact of this change was discussed in the following bug reports:

https://bugs.documentfoundation.org/show_bug.cgi?id=130847

https://bugs.documentfoundation.org/show_bug.cgi?id=134151

2) Another example is the addition of the Alt + 5 shortcut key to activate the Sidebar pane:

https://bugs.documentfoundation.org/show_bug.cgi?id=158112

3) PDF files are now exported to the most recently used directory, rather than the directory of the active document. This change in LibreOffice's behavior was unexpected and caused inconvenience.

https://bugs.documentfoundation.org/show_bug.cgi?id=165917

4) Additionally, the removal of the "Add to Dictionary" option from the context menu caused inconvenience to many users:

https://bugs.documentfoundation.org/show_bug.cgi?id=166689

Although this particular issue was quickly resolved within five days, it still raises a critical question: Who is responsible for testing and verifying such changes before they are merged? If the "Add to Dictionary" option is not available on right click, proof reading would have become impossible.

To ensure quality and minimize unintended consequences, I recommend establishing a more robust review and testing protocol for code changes.