[Community Help Wiki] Update of "ReportingBugs" by penalvch

[Help Ubuntu]

Dear Wiki user,

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

The "ReportingBugs" page has been changed by penalvch:
http://help.ubuntu.com/community/ReportingBugs?action=diff&rev1=276&rev2=277

Comment:
Due to LP#1402095 added support note on EoL releases, and upgrading with third-party software installed.

  
  == All bug reports ==
  
+  * '''Please do not file bug reports about End-of-Life operating systems.''' <<BR>> This includes release of Ubuntu, and alternative operating systems. Expecting Ubuntu to provide interoperability with an insecure, end-of-life operating system is simply irresponsible, and inconsiderate of the finite resources of the Ubuntu Community. Information regarding supported Ubuntu releases are available [[https://wiki.ubuntu.com/Releases|here]]. Please see the website of the vendor of the operating system for EOL and support information.
   * '''Please do not speculate on what you think is or isn't a duplicate report.''' <<BR>> For example, "I googled around and found bug report number..." This is largely unhelpful as it tends not to be a duplicate, and already has been or easily done by triagers and developers. Instead, if you are the original reporter, ensuring the report has all the requested testing information performed would be the fastest way to ensure your bug is resolved as soon as possible. If you are not the original reporter, it's best to file a new report, so that necessary debugging attachments are reviewed. It is a common misconception that filing a potential duplicate report is wasteful. Filing a new report is quite helpful, and is preferred to ease triaging.
   * '''Please do not quote Wikipedia and other non-primary resource information as fact on [[Launchpad]].'''
   * '''Please do not complain because someone sent what one perceives to be a automated or "canned" response'''. <<BR>> If the response is asking you to do something that you have't done (ex. test the latest development release, file a new report, etc.) do it, as it would get you closer to having your bug fixed faster. Complaining about this is inconsiderate of the Ubuntu triagers and developers who are saving time in comparison to hand typing every single character in an e-mail that goes out their inbox.
@@ -303, +304 @@

   * '''Please keep the bug report as objective as possible.''' <<BR>> It is desired for you to provide a fact based, technical impact statement on you, your environment, and the potential or actual impact on the community at large.
   * '''Please provide all relevant information from [[https://wiki.ubuntu.com/DebuggingProcedures]] when you first report your bug'''. <<BR>> This is one of the top reasons why bugs do not get marked [[https://wiki.ubuntu.com/Bugs/Status|Triaged]], as the minimum requirements for triaging, and dealing with the problem by a developer are not provided.
   * '''Please avoid arguing with triagers and developers.''' <<BR>> If a triager or developer asks you to provide information, just provide the information as requested. An example of this is claiming exemption because you or someone else filed a bug report upstream or downstream (which is publicly viewable, and has no restrictions on who can file). You are being asked for this information so that it would provide more information on how to fix the problem. Also, not everyone has access to the hardware you are reporting against, or reproduce the problem as advised in the report. Having you provide the information helps eliminate the difficulty in fixing your bug. If you have a strong disagreement with what a triager or developer is asking of you, please resolve it with them directly via personal message, not on the bug report. This avoids turning a bug development report into a “let’s talk about talking about the problem” tangent, distracting from having your bug solved. The Ubuntu community takes a favor to objective, technical discourse.
-  * '''Please do not report bugs about software in [[PPA]]s.''' <<BR>> This is because software in PPAs are not provided by the official Ubuntu repositories. Instead, the PPA homepage would have a contact point and preference of the PPA provider. The exception is [[LibreOffice]] as per [[https://lists.launchpad.net/libreoffice/msg00072.html|this mail]], as LibreOffice is too big to be tracked via email: as described in the mail, file a bug on Launchpad with tag `ppa`.
+  * '''Please do not report bugs about software in [[PPA]]s.''' <<BR>> This is because software in PPAs are not provided by the official Ubuntu repositories, and in turn not supported. Instead, the PPA homepage would have a contact point and preference of the PPA provider. The exception is [[LibreOffice]] as per [[https://lists.launchpad.net/libreoffice/msg00072.html|this mail]], as LibreOffice is too big to be tracked via email: as described in the mail, file a bug on Launchpad with tag `ppa`.
+  * '''Please do not report upgrade failures when you have installed software that is self-compiled, from a third party deb not provided by the Ubuntu repositories, or from a PPA.''' In order to maximize your upgrade success, all this software would need to be uninstalled, or replaced with the corresponding software from the Ubuntu repositories if it is mandatory to keep.
   * '''Please do not add project tasks to bug reports that are invalid because they are not supported'''. <<BR>> For example, if you were using the LibreOffice PPA and reported a bug against the package libreoffice (Ubuntu), which would be marked Status Invalid, please do not add the Launchpad Project [[https://launchpad.net/df-libreoffice|df-libreoffice]] to the report, or change the package libreoffice (Ubuntu) to the project df-libreoffice. The purposes of adding the upstream project to a report is to track valid bugs in Ubuntu that are valid upstream, and may have been reported upstream, not to start another upstream bug tracker.
   * '''When posting new comments to a Launchpad report, please do not reply and include every past comment made.''' <<BR>> Doing so makes it onerous to read a report, and is wasteful. Instead just make your new comment, or just include the relevant portion of a previous comment you are responding to.
   * '''Please do not announce in a report you did not file, that you filed a new report.'''