|
⇤ ← Revision 1 as of 2011-03-04 20:30:22
Size: 1729
Comment: initial page
|
Size: 1731
Comment: Beautifying
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 13: | Line 13: |
| you can read this [[http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/2009/03/02|interesting post]] | You can read this [[http://www.chiark.greenend.org.uk/ucgi/~cjwatson/blosxom/2009/03/02|interesting post]] |
| Line 15: | Line 15: |
| == finding information == | == Finding information == |
| Line 24: | Line 24: |
| == different way to work on bug reports == === browse bug report === read [[HowtoUseBTS#QueryingBugReports]] |
== Different ways to work on bug reports == === Browse bug reports === Read [[HowtoUseBTS#QueryingBugReports]] |
| Line 28: | Line 28: |
| === report bug === | === Report bugs === |
| Line 33: | Line 33: |
| You have many possibility with [[BugTriage]] | You have many possibility with [[BugTriage]] |
| Line 35: | Line 35: |
| === 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. |
=== 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. |
Contents
First things first
All the help is welcome. We lack man power to handle bug reports.
So don't hesitate to try a few things written here. You'll see, it is 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.
You can read this interesting post
Finding information
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.
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.
Search engines can some times be useful resources in tracking down if other distributions or people have seen the same bug.
Different ways to work on bug reports
Browse bug reports
Read HowtoUseBTS#QueryingBugReports
Report bugs
So learn to reportbug and read HowtoUseBTS#ReportingBugReports
Bug Triaging
You have many possibility 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.