![]() |
|
Technical threads All discussions about technical issues |
|
Thread Tools | Display Modes |
#11
|
|||
|
|||
![]()
IMHO we need a "guideline" for bug reports, e.g. https://developer.mozilla.org/en/Bug_writing_guidelines
We really need quality bug reports, especially as the developers are not part of the system, i.e. they do not interact with the reporter, they only read the report. A low quality report might be written in 1-2 minutes, but the workload for the admins or developers are increased considerably. If one wants to report a bug that he things is important he should take the time to write a high quality report. For aircraft system this includes researching the subject and providing evidence. There are so many bug reports on aircraft systems in this forum that a simply wrong and not or bad researched. For game bugs this requires a step by step instruction to reproduce the bug. The reporter has to provide (depending on type of issue) - step by step instruction to reproduce the issue - screenshots to display the issue - mission files/tracks to allow easier reproduction of the issue - documents/sources to proof the issue Last edited by 41Sqn_Banks; 04-04-2012 at 09:29 AM. |
|
|