 |
Other languages Deutsch ; English ; Español ; Français ; Nederlands ; Türkçe; português brasileiro ; |
Contents
What is Bugzilla
Bugzilla is a “Defect Tracking System” or “Bug-Tracking System”. Defect Tracking Systems allow individuals or groups of developers to keep track of outstanding bugs in their product effectively. Most commercial defect-tracking software vendors charge enormous licensing fees. Despite being “free”, Bugzilla has many features its expensive counterparts lack. Consequently, Bugzilla has quickly become a favourite of hundreds of organizations across the globe.
What Does Bugzilla Do?
- Track bugs and code changes
- Communicate with team mates
- Submit and review patches
- Manage quality assurance (QA)
Bugzilla can help you get a handle on the software development process.
Successful projects often are the result of successful organization and communication.
Bugzilla is a powerful tool that will help your team get organized and communicate effectively.
More about Bugzilla
This tool is a product of the Mozilla foundation. More information on www.bugzilla.org
How to report a bug
Please check How to report a bug (properly)
How to describe a bug
This part is VERY important because with your description, the developer must be able to reproduce your bug.
To describe a bug, you must give:
- Description of problem:
| While I was trying to... (I explain what I was doing). The ... crashed by displaying (I explain the bug with all the details I can provide!). Here is my error message : "..." * Environment * Distribution: $version ($ cat /etc/mageia-release) * Kernel: $version ($ uname -rm) * Name_of_the_packages_of_the_bug: $version ($ rpm -qa | grep name_of_the_package) * Desktop environment: $version (KDE, GNOME, LXDE, ...) * Xorg: $version (# cat /var/log/Xorg.0.log | grep "X Window") * My hardware (if needed) * Graphic card (if needed) * My hard drive chipset (if needed) * My peripherals (if needed) |
- Version-Release number of selected component (if applicable)
- How reproducible
- Steps to Reproduce
- Give each...
- ...step required to...
- ...reproduce the bug!
| Warning! Now that you have reported a bug, remember to follow it up and reply to the dev/packager about it. |
Flags
Some of our previously used Whiteboard strings and Keywords, have now been replaced by flags.
If you click on "set flags" or "more flags", you can see which ones are available, apart from the ones that are already set. Once a flag is set, it is preceded with the part before the @ of the e-mail address of the person who set it.
Not every flag can be added in every bug report, and some flags can only be requested, or set to + or -, by some users, like packagers, testers and triagers.
affects_mga9
For bugs that not only affect the higher version they are filed against, but also Mageia 9. Set to "+", this replaces the "MGA9TOO" string on the whiteboard. Madb now looks for affects_mga9+ instead of for MGA9TOO
affects_mga9 ? Does this bug occur in Mageia 9, too?
affects_mga9 + This bug occurs in Mageia 9, too.
affects_mga9 - This bug does not occur in Mageia 9.
in_errata10
For documentation to be added or improved in the Mageia 10 Errata:
in_errata10 ? Please add or improve in the Errata (was FOR_ERRATA10).
in_errata10 + It has been added/improved (was IN_ERRATA10).
in_errata10 - It should not be in Errata 10.
in_release_notes10
For bugs that should be mentioned in the Mageia 10 Release Notes:
in_release_notes10 ? Please add or improve in the Release Notes (was FOR_RELEASENOTES10).
in_release_notes10 + It has been added/improved (was IN_RELEASENOTES10).
in_release_notes10 - It should not be in these release notes.
in_wiki
For documentation to be added or improved in the Mageia Wiki:
in_wiki ? Please add or improve in our Wiki.
in_wiki + It has been added/improved.
in wiki - It should not be in our Wiki.
need_info
Usually in combination with the NEEDINFO status. The user who needs to provide additional information can be added in this flag. Instead of typing the e-mail address, you can type three or more characters of this address, or of his Mageia ID, or of his name in Mageia Identity, to see a list of users who share the same characters, and select the correct one.
needinfo ? [optional: user's e-mail address] Please provide the requested information.
needinfo + The requested information has been added to the bug report.
needinfo - The information can't or won't be supplied.
Instead of needinfo+, it is also possible to remove the flag after giving the required feedback.
Instead of needinfo-, a user can remove his e-mail address from the flag if he can't or won't supply the information.
test_passed_mga9_32
For QA team, if they decide to use it, to replace the MGA9-32-OK string on the whiteboard. Multiple test_passed_mga9_32 flags can be set in the same bug report, this is especially useful when testing kernels and other packages that need wider testing.
xxx:test_passed_mga9_32? [optional: one or more e-mail addresses] request from xxx to test this update on i586. With e-mail addresses: ask specific persons - for instance a bug reporter and people who commented they hit the same bug.
yyy:test_passed_mga9_32+ : The update passed the test done by yyy on i586
zzz:test_passed_mga9_32- : The update failed the test done by zzz on i586
test_passed_mga9_64
For QA team, if they decide to use it, to replace the MGA9-64-OK string on the whiteboard. Multiple test_passed_mga9_64 flags can be set in the same bug report, this is especially useful when testing kernels and other packages that need wider testing.
xxx:test_passed_mga9_64? [optional: one or more e-mail addresses] request from xxx to test this update on x86_64. With e-mail addresses: ask specific persons - for instance a bug reporter and people who commented they hit the same bug.
yyy:test_passed_mga9_64+ : The update passed the test done by yyy on x86_64
zzz:test_passed_mga9_64- : The update failed the test done by zzz on x86_64
