KnowledgeBase
|
Size: 5537
Comment: Added link to new page Bugs/ApportRetraces
|
Size: 5755
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| [[Include(BugSquad/Header)]] | <<Include(BugSquad/Header)>> |
| Line 3: | Line 3: |
| ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''[[BR]][[TableOfContents]]|| | ||<tablestyle="float:right; font-size: 0.9em; width:40%; background:#F1F1ED; margin: 0 0 1em 1em;" style="padding:0.5em;">'''Contents'''<<BR>><<TableOfContents>>|| |
| Line 7: | Line 7: |
| [:MeetingLogs/openweekhardy/TriageBugs2:Triaging Class] - Class given at Ubuntu Open Week in May of 2008 by PedroVillavicencio | [[MeetingLogs/openweekhardy/TriageBugs2|Triaging Class]] - Class given at Ubuntu Open Week in May of 2008 by PedroVillavicencio |
| Line 9: | Line 9: |
| [:MeetingLogs/openweekhardy/ReportBugs2:Reporting Bugs Class] - Class given at Ubuntu Open Week in May of 2008 by BrianMurray | [[MeetingLogs/openweekhardy/ReportBugs2|Reporting Bugs Class]] - Class given at Ubuntu Open Week in May of 2008 by BrianMurray |
| Line 11: | Line 11: |
| [:Bugs/HowToTriage:How to Triage] - General summary of how to properly triage bug reports | [[Bugs/HowToTriage|How to Triage]] - General summary of how to properly triage bug reports |
| Line 13: | Line 13: |
| [:Bugs/BestPractices:Best Practices] - Useful Do's and Don't's for bug reporting | [[Bugs/BestPractices|Best Practices]] - Useful Do's and Don't's for bug reporting |
| Line 15: | Line 15: |
| [:Bugs/Improving:Improving a Report] - How to improve a bug report - an essential part of triaging | [[Bugs/Improving|Improving a Report]] - How to improve a bug report - an essential part of triaging |
| Line 17: | Line 17: |
| [:Bugs/Status:Managing Status] - When Ubuntu uses which bug status and what they mean to us | [[Bugs/Status|Managing Status]] - When Ubuntu uses which bug status and what they mean to us |
| Line 19: | Line 19: |
| [:Bugs/Importance:Managing Importance] - The criteria for setting a bug's importance and definitions | [[Bugs/Importance|Managing Importance]] - The criteria for setting a bug's importance and definitions |
| Line 21: | Line 21: |
| [:Bugs/Description:Improving the Bug Description] - Ways to communicate useful information in the bug description | [[Bugs/Description|Improving the Bug Description]] - Ways to communicate useful information in the bug description |
| Line 23: | Line 23: |
| [:Bugs/Assignment:Assigning Bugs] - When to assign bug reports to individuals or teams | [[Bugs/Assignment|Assigning Bugs]] - When to assign bug reports to individuals or teams |
| Line 25: | Line 25: |
| [:Bugs/MarkingDuplicate:Marking a Duplicate] - How and when to mark a bug as a duplicate of another | [[Bugs/MarkingDuplicate|Marking a Duplicate]] - How and when to mark a bug as a duplicate of another |
| Line 27: | Line 27: |
| [:Bugs/Watches:Bug Watches] - How to set up Launchpad to monitor bug reports in other bug tracking systems. | [[Bugs/Watches|Bug Watches]] - How to set up Launchpad to monitor bug reports in other bug tracking systems. |
| Line 29: | Line 29: |
| [:DebuggingProcedures:Debugging Procedures] - Common procedures for debugging types of problems or packages | [[DebuggingProcedures|Debugging Procedures]] - Common procedures for debugging types of problems or packages |
| Line 31: | Line 31: |
| [:Bugs/ApportRetraces:Apport Retraces] - How to understand and use Apport retraces (based on a MOTU/School class by EmmetHikory) | [[Bugs/ApportRetraces|Apport Retraces]] - How to understand and use Apport retraces (based on a MOTU/School class by EmmetHikory) |
| Line 35: | Line 35: |
| [:Bugs/Responses:Standard Replies] - A collection of frequently used replies to bug reports setup for easy copy and pasting | [[Bugs/Responses|Standard Replies]] - A collection of frequently used replies to bug reports setup for easy copy and pasting |
| Line 37: | Line 37: |
| [:Bugs/Checklist:Checklist] - A checklist of common actions to perform for bug reports | [[Bugs/Checklist|Checklist]] - A checklist of common actions to perform for bug reports |
| Line 39: | Line 39: |
| [:Bugs/Tags:Bug Tags] - In Launchpad it is possible to add "tags" or keywords to a bug report - this is Ubuntu's standardized list | [[Bugs/Tags|Bug Tags]] - In Launchpad it is possible to add "tags" or keywords to a bug report - this is Ubuntu's standardized list |
| Line 41: | Line 41: |
| [:DeveloperResponsibilities:Developer Responsibilities] - Are you trying to find a developer familiar with a particular package or subsystem? Find out how here! | [[DeveloperResponsibilities|Developer Responsibilities]] - Are you trying to find a developer familiar with a particular package or subsystem? Find out how here! |
| Line 43: | Line 43: |
| [https://help.launchpad.net/UsingMaloneEmail Modifying bugs via e-mail] - Malone, Ubuntu's bug tracker, has an e-mail interface for working with bugs | [[https://help.launchpad.net/UsingMaloneEmail|Modifying bugs via e-mail]] - Malone, Ubuntu's bug tracker, has an e-mail interface for working with bugs |
| Line 45: | Line 45: |
| [:Bugs/HowToFilter:Filtering bug mail] - Example procmail rules for filtering any bug e-mail you get | [[http://launchpad.net/launchpad-gm-scripts|Greasemonkey scripts for Launchpad]] - A project that collects Greasemonkey scripts that Launchpad users find useful [[Bugs/HowToFilter|Filtering bug mail]] - Example procmail rules for filtering any bug e-mail you get |
| Line 49: | Line 51: |
| [http://isv-image.ubuntu.com/vmware/ VMware Images] - Images available for recreating some bugs - username and password are ubuntu | [[http://isv-image.ubuntu.com/vmware/|VMware Images]] - Images available for recreating some bugs - username and password are ubuntu |
| Line 51: | Line 53: |
| [http://people.ubuntu.com/~bryce/Plots/ Ubuntu bug graph] - pretty pictures showing the quantity of bugs reported about Ubuntu * [http://people.ubuntu.com/~brian/testing_graphs/ List of all graphs] - Packages with 100+ bugs are currently being graphed * [http://people.ubuntu.com/~brian/complete-graphs/ List of complete graphs] - These graphs are more complete as they capture each possible bug status or importance |
[[http://people.ubuntu.com/~bryce/Plots/|Ubuntu bug graph]] - pretty pictures showing the quantity of bugs reported about Ubuntu * [[http://people.ubuntu.com/~brian/testing_graphs/|List of all graphs]] - Packages with 100+ bugs are currently being graphed * [[http://people.ubuntu.com/~brian/complete-graphs/|List of complete graphs]] - These graphs are more complete as they capture each possible bug status or importance |
| Line 55: | Line 57: |
| [http://people.ubuntu.com/~brian/reports/ Bug query reports] - Bug queries using the bughelper suite that are run daily. Reports run include: * bugs with [http://people.ubuntu.com/~brian/reports/gt2dups more than 2 duplicates] * bugs with [http://people.ubuntu.com/~brian/reports/gt5comments more than 5 comments] * bugs with [http://people.ubuntu.com/~brian/reports/gt5subscribers more than 5 subscribers] * bugs with [http://people.ubuntu.com/~brian/reports/database/bugs-with-most-duplicates.html the most duplicates] * oldest [http://people.ubuntu.com/~brian/reports/database/oldest-new-ubuntu-bugs.html New bug reports] * oldest [http://people.ubuntu.com/~brian/reports/database/oldest-confirmed-ubuntu-bugs.html Confirmed bug reports] * oldest [http://people.ubuntu.com/~brian/reports/database/oldest-inprogress-ubuntu-bugs.html In Progress bug reports] * oldest [http://people.ubuntu.com/~brian/reports/database/oldest-fixcommitted-ubuntu-bugs.html Fix Committed bug reports] |
[[http://people.ubuntu.com/~brian/reports/|Bug query reports]] - Bug queries using the bughelper suite that are run daily. Reports run include: * bugs with [[http://people.ubuntu.com/~brian/reports/gt2dups|more than 2 duplicates]] * bugs with [[http://people.ubuntu.com/~brian/reports/gt5comments|more than 5 comments]] * bugs with [[http://people.ubuntu.com/~brian/reports/gt5subscribers|more than 5 subscribers]] * bugs with [[http://people.ubuntu.com/~brian/reports/database/bugs-with-most-duplicates.html|the most duplicates]] * oldest [[http://people.ubuntu.com/~brian/reports/database/oldest-new-ubuntu-bugs.html|New bug reports]] * oldest [[http://people.ubuntu.com/~brian/reports/database/oldest-confirmed-ubuntu-bugs.html|Confirmed bug reports]] * oldest [[http://people.ubuntu.com/~brian/reports/database/oldest-inprogress-ubuntu-bugs.html|In Progress bug reports]] * oldest [[http://people.ubuntu.com/~brian/reports/database/oldest-fixcommitted-ubuntu-bugs.html|Fix Committed bug reports]] |
| Line 65: | Line 67: |
| [http://packages.ubuntu.com/hardy/devscripts Ubuntu Developer Scripts] - The devscripts package includes a lot of useful tools including rmadison which tells you the current package version for every supported release of Ubuntu. | [[http://packages.ubuntu.com/hardy/devscripts|Ubuntu Developer Scripts]] - The devscripts package includes a lot of useful tools including rmadison which tells you the current package version for every supported release of Ubuntu. |
| Line 69: | Line 71: |
| [https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&field.has_no_package=on New and No Package] - These bugs need triaging and a package | [[https://bugs.launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=NEW&field.importance%3Alist=UNKNOWN&field.importance%3Alist=UNDECIDED&assignee_option=any&field.assignee=&field.bug_reporter=&field.bug_supervisor=&field.bug_commenter=&field.subscriber=&field.component-empty-marker=1&field.status_upstream-empty-marker=1&field.omit_dupes.used=&field.omit_dupes=on&field.has_patch.used=&field.has_cve.used=&field.tag=&field.tags_combinator=ANY&field.has_no_package.used=&field.has_no_package=on|New and No Package]] - These bugs need triaging and a package |
| Line 71: | Line 73: |
| [https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=New&field.importance%3Alist=Undecided&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.component%3Alist=1&field.component%3Alist=2&field.has_no_package= New Bugs] - These bugs have not been triaged at all | [[https://launchpad.net/ubuntu/+bugs?field.searchtext=&orderby=-datecreated&search=Search&field.status%3Alist=New&field.importance%3Alist=Undecided&field.assignee=&field.bug_reporter=&field.omit_dupes=on&field.has_patch=&field.component%3Alist=1&field.component%3Alist=2&field.has_no_package=|New Bugs]] - These bugs have not been triaged at all |
| Line 73: | Line 75: |
| [https://launchpad.net/bugs/bugtrackers/ Bugtrackers in Launchpad] - Useful for finding lists of links between bugs reported in Launchpad and upstream bug reports | [[https://launchpad.net/bugs/bugtrackers/|Bugtrackers in Launchpad]] - Useful for finding lists of links between bugs reported in Launchpad and upstream bug reports |
Contents |
Working with Bugs
Triaging Class - Class given at Ubuntu Open Week in May of 2008 by PedroVillavicencio
Reporting Bugs Class - Class given at Ubuntu Open Week in May of 2008 by BrianMurray
How to Triage - General summary of how to properly triage bug reports
Best Practices - Useful Do's and Don't's for bug reporting
Improving a Report - How to improve a bug report - an essential part of triaging
Managing Status - When Ubuntu uses which bug status and what they mean to us
Managing Importance - The criteria for setting a bug's importance and definitions
Improving the Bug Description - Ways to communicate useful information in the bug description
Assigning Bugs - When to assign bug reports to individuals or teams
Marking a Duplicate - How and when to mark a bug as a duplicate of another
Bug Watches - How to set up Launchpad to monitor bug reports in other bug tracking systems.
Debugging Procedures - Common procedures for debugging types of problems or packages
Apport Retraces - How to understand and use Apport retraces (based on a MOTU/School class by EmmetHikory)
Bug Tools
Standard Replies - A collection of frequently used replies to bug reports setup for easy copy and pasting
Checklist - A checklist of common actions to perform for bug reports
Bug Tags - In Launchpad it is possible to add "tags" or keywords to a bug report - this is Ubuntu's standardized list
Developer Responsibilities - Are you trying to find a developer familiar with a particular package or subsystem? Find out how here!
Modifying bugs via e-mail - Malone, Ubuntu's bug tracker, has an e-mail interface for working with bugs
Greasemonkey scripts for Launchpad - A project that collects Greasemonkey scripts that Launchpad users find useful
Filtering bug mail - Example procmail rules for filtering any bug e-mail you get
BugHelper - bughelper is a tool to help us triage bugs by parsing reports for clues about the type of bug and then sharing those clues with other triagers
VMware Images - Images available for recreating some bugs - username and password are ubuntu
Ubuntu bug graph - pretty pictures showing the quantity of bugs reported about Ubuntu
List of all graphs - Packages with 100+ bugs are currently being graphed
List of complete graphs - These graphs are more complete as they capture each possible bug status or importance
Bug query reports - Bug queries using the bughelper suite that are run daily. Reports run include:
bugs with more than 2 duplicates
bugs with more than 5 comments
bugs with more than 5 subscribers
bugs with the most duplicates
oldest New bug reports
oldest Confirmed bug reports
oldest In Progress bug reports
oldest Fix Committed bug reports
Ubuntu Developer Scripts - The devscripts package includes a lot of useful tools including rmadison which tells you the current package version for every supported release of Ubuntu.
Launchpad Bug Queries
New and No Package - These bugs need triaging and a package
New Bugs - These bugs have not been triaged at all
Bugtrackers in Launchpad - Useful for finding lists of links between bugs reported in Launchpad and upstream bug reports
BugSquad/KnowledgeBase (last edited 2020-12-19 16:15:33 by koen-beek)