Changes between Version 21 and Version 22 of ReportingBugs


Ignore:
Timestamp:
Mar 26, 2023, 8:29:44 AM (6 months ago)
Author:
pulkomandy
Comment:

Add a note asking bug reporters to not fill in the keywords, milestone and priority fields.

Legend:

Unmodified
Added
Removed
Modified
  • ReportingBugs

    v21 v22  
    55 1. Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).
    66 1. Mention which '''revision from GIT''' you are running. You can find this out in the 'About Haiku' application, in the Deskbar menu. Also mention what '''kind of Haiku build''' you are testing (32 or 64bit, gcc2 or gcc7 only, ...). The downloadable images are named accordingly, for a self-built image you should know how you built it.
     7 1. Select the appropriate "component" for your bug. IF you don't know or can't find the right one, leave the field empty, and one of the developers will set it. Select the version of Haiku you are running in the "version" field. Do not fill in the other fields: milestone, priority, keywords, etc. These are reserved for use by the developers for organizing the tickets.
    78 1. After the bug has been reported, a developer will look at your bug. Remember, we are all volunteers, and as such, sometimes a bug report might go unanswered for a while. Adding new information when it becomes available usually helps getting a bug picked up quicker, but do not try to 'bump' the bug up by adding non-informative comments.
    8  1. Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Stay around to answer these. Consider your participation 'done' when the bug is marked as 'fixed'. Together we can improve Haiku, bit by bit. 
     9 1. Remember, reporting a bug is not something you spend a little time on and then you are done. If you reported a bug, then you are part of the Haiku development process. Developers might come up with questions while they are trying to fix your bug. Stay around to answer these. Consider your participation 'done' when the bug is marked as 'fixed'. Together we can improve Haiku, bit by bit.
    910 1. The remainder of guidelines depend on the type of bug:   
    1011  1. [#ApplicationBugs applications]