[Ubuntu Wiki] Update of "LibreOfficeBugWrangling" by bjoern-michaelsen

[Ubuntu Wiki]

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Ubuntu Wiki" for change notification.

The "LibreOfficeBugWrangling" page has been changed by bjoern-michaelsen:
http://wiki.ubuntu.com/LibreOfficeBugWrangling?action=diff&rev1=2&rev2=3

Comment:
all due credit: original text is by Christopher Penalver, I just pasted it.

   * Sample bug reporting template: <<BR>> 
  ||<tablestyle="background-color: #eee"> 1) lsb_release -rd <<BR>> <<BR>> 2) apt-cache policy libreoffice-writer <<BR>> <<BR>> 3) What is expected to happen in Writer is <PRECISE, STEP-BY-STEP INSTRUCTIONS>. <<BR>> <<BR>> 4) What happened instead is... <<BR>> <<BR>> WORKAROUND: Perform the following steps:...||
   * Please do not stack multiple issues into one bug.
-  * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. Especially, if you have not completed the relevent, below mentioned debugging procedures, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.
+  * Please do not complain about how long it takes to fix a bug, the severity of your bug is high so it should be fixed immediately, "I cannot believe it's not fixed...", etc. Especially, if you have not completed the relevant, below mentioned debugging procedures, let alone contributed code upstream. This type of behavior is unconstructive, irritating to others who read your E-Mail, and spammy. We all want to see every bug fixed as soon as possible! Naturally, bugs being fixed is limited to reproducibility and clarity of the bug report, the actual impact the bug has on the community, and available developer resources.
  
  = Debugging procedure =
  == Document Issues ==