launchpad development|
⇤ ← Revision 1 as of 2009-08-10 15:44:52
Size: 1603
Comment: New page.
|
← Revision 2 as of 2009-08-16 19:50:43 ⇥
Size: 1663
Comment: Update example to make it clear that Launchpad is open source.
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 17: | Line 17: |
| I'll sponsor anyone who wants to submit a patch. | I'll sponsor anyone who wants to submit a patch. (Launchpad is open source; see https://dev.launchpad.net/) |
This page is about how to handle and triage Launchpad-related bugs. For information about the Launchpad bug tracker's code, please see Bugs instead. Ask for help right away if you have any questions. |
How to File a Bug About Launchpad
TODO: There should be a section about this. Possibly it should be in the Help Wiki and linked to from here. Anyway, please help us fill in this section
How to Respond to a Bug
When responding to a bug report, please tell the reporter how they can help fix it. If the bug looks easy, then give an authoritative statement that it is easy to fix, give clear steps to fix it, and (most importantly) say that help is available:
This is an easy fix. Just:
A) ...
B) ...
C) ...
I'll sponsor anyone who wants to submit a patch. (Launchpad is open source; see https://dev.launchpad.net/)If you yourself cannot sponsor a patch, that's okay -- just say that help is available and point the reporter to https://dev.launchpad.net/Help. Even if the bug doesn't look easy, still point out that the reporter can get involved in fixing it and point them to where they can get help.
As Maris Fogels points out, expect the 1000/10/1 rule: we'll get 1 patch for every 10 commentors and every 1000 viewers. That's okay: one patch is still worth a lot.
How We Triage Launchpad Bugs
See BugTriage.
