Changes between Version 15 and Version 16 of ReportingBugs


Ignore:
Timestamp:
Aug 24, 2018, 7:00:37 AM (6 years ago)
Author:
pulkomandy
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • ReportingBugs

    v15 v16  
    44 1. Attempt to '''reproduce your issue''' on the current revision of Haiku. Pre-built images for testing purposes are [http://download.haiku-os.org/ available].
    55 1. Include basic information such as how you are testing Haiku (on real hardware, on VMWare, on QEMU, etc.).
    6  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 (gcc2, gcc4, gcc2hybrid, gcc4hybrid). The downloadable images are named accordingly, for a self-built image you should know how you built it.
     6 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.
    77 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.
    88 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.