|
Size: 2171
Comment: Moved Link: complying with 'Links to external sites' in EditorGuide
|
Size: 2722
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 11: | Line 11: |
| Often team maintained projects have an IRC channel and/or a mailing list for the team. You can use these as resources when you are triaging bugs. If they have an IRC channel you may well find other users around at the same time that you can enlist to try to reproduce a bug you're having trouble reproducing or other people to advise you on issues with bugs. | * You can find informations about a package on the '''[[https://tracker.debian.org/|tracker]]''' like * the [[DDPO|maintainer's DDPO]], * the history of the upload, * the homepage of upstream, * a link to [[Salsa]] (VCS), * a link to [[https://en.wikipedia.org/wiki/Launchpad_(website)|ubuntu's launchpad]] and much more. |
| Line 13: | Line 18: |
| Upstream normally have a mailing list for their software even if they don't have a bug tracker and they may have an IRC channel too. Again an IRC channel might be useful to find people who can help you to reproduce or rule out bugs. | * [[Teams|Team maintained projects]] have specific informations and resources. You can use these as resources when you are triaging bugs. * some times they have a policy. * They often have a mailing list for the team. * If they have an IRC channel you may well find other users around at the same time that you can enlist to try to reproduce a bug you're having trouble reproducing or other people to advise you on issues with bugs. |
| Line 15: | Line 23: |
| Search engines can some times be useful resources in tracking down if other distributions or people have seen the same bug. | * Upstream normally have their own resources. * a homepage * a mailing list for their software * a bug tracker * and they may have an IRC channel too. Again an IRC channel might be useful to find people who can help you to reproduce or rule out bugs. * Search engines can some times be useful resources in tracking down if other distributions or people have seen the same bug. You can also find informations on their bug trackers * [[https://bugzilla.readthedocs.io/en/5.0/using/index.html|bugzilla]] * [[https://launchpad.net/ubuntu|ubuntu]] * [[https://bugzilla.redhat.com/index.cgi|redhat]] |
| Line 34: | Line 52: |
== External Links == Interesting blog post about bug triaging: https://www.chiark.greenend.org.uk/~cjwatson/blog/bug-triage-rants.html |
Contents
First things first
All help is welcome, we lack people power to handle bug reports so don't hesitate to try a few things written here. You'll see it's rewarding to tweak bugs.
First you have to get to know the BTS. You can also read how to use the BTS.
Bug reports are designed to help the maintainer to have a better package.
Finding information
You can find informations about a package on the tracker like
the maintainer's DDPO,
- the history of the upload,
- the homepage of upstream,
a link to Salsa (VCS),
a link to ubuntu's launchpad and much more.
Team maintained projects have specific informations and resources. You can use these as resources when you are triaging bugs.
- some times they have a policy.
- They often have a mailing list for the team.
- If they have an IRC channel you may well find other users around at the same time that you can enlist to try to reproduce a bug you're having trouble reproducing or other people to advise you on issues with bugs.
- Upstream normally have their own resources.
- a homepage
- a mailing list for their software
- a bug tracker
- and they may have an IRC channel too. Again an IRC channel might be useful to find people who can help you to reproduce or rule out bugs.
- Search engines can some times be useful resources in tracking down if other distributions or people have seen the same bug. You can also find informations on their bug trackers
Different ways to work on bug reports
Browse bug reports
Read HowtoUseBTS#QueryingBugReports. You can also use UDD Bugs search to select bugs corresponding to your criteria.
Report bugs
So learn to reportbug and read HowtoUseBTS#ReportingBugReports.
Bug Triaging
You have many possibilities with BugTriage.
Closing bug reports
The best is to write a patch and wait for the maintainer to close the bug once the package is updated with your patch.
You can also close bug reports if a new version fixed the problem, but remember to say in which version it was fixed.
You can close bug reports that are tagged "moreinfo" since more than a year, if no info has been provided and it seems unreproducible.