Community bugtracker is up @ il2bugtracker.com

[Ataros]

Got an e-mail from luthier:

Ilya Shevchenko
Добрый день,
Спасибо, очень приветствуем!
Не очень уверен в системе Redmine, так как она вроде не совсем для багов - но будем следить!
С уважением,
Илья

Translation:
"Good afternoon,
Thank you, the tracker is very welcome!
I am not very sure about Redmine system as it seems it is not exactly for bugtracking - but we will watch it!
Regards,
Ilya"

[Dano]

Excellent stuff, my thanks to all involved

[41Sqn_Banks]

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

[Ataros]

Originally Posted by 41Sqn_Banks

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

S! Added to the 1st post of the thread.

[SG1_Lud]

Originally Posted by 41Sqn_Banks

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

@Ataros; I am publishing and mantaining a Spanish translation of the guidelines for reporting and tracking bugs here: http://sg1.es/foro/viewtopic.php?f=54&t=3267

[Allons!]

Ataros, shall we transfer the already mentioned bugs to the Tracking system? Then, i would link the bugreport to this forum for then we wouldnt have to transfer all the graphics (screenshots etc.) as well.

[Ataros]

Originally Posted by Allons!

Ataros, shall we transfer the already mentioned bugs to the Tracking system? Then, i would link the bugreport to this forum for then we wouldnt have to transfer all the graphics (screenshots etc.) as well.

I would leave it to everyone to decide unless the devs ask us specifically to do or not to do this. If you feel like you know about very important bug that you want to be fixed ASAP post it. But do a search to make sure it was not reported earlier and fill in Category.

I think it is possible to give links to this forum for pictures, videos, etc.

[Ataros]

Please check bugs with status "feedback" and provide more information. As in one example devs have to comment:

Sorry, but a good bug report should contain more info. What aircraft?

See Kodiak's guidelines above before posting please and be very very extremely detailed.

[Ataros]

The devs changed status of some bugs and commented on them.

Important!

Please stop double-posting the bugs and make sure you select the right Category before posting. If luthier has to reject double posted tasks and assign category himself this tool will not help development but will slow it down instead.

Let's make sure we do it right!

[albx]

Originally Posted by Ataros

The devs changed status of some bugs and commented on them.

Important!

Please stop double-posting the bugs and make sure you select the right Category before posting. If luthier has to reject double posted tasks and assign category himself this tool will not help development but will slow it down instead.

Let's make sure we do it right!

I think we got a very good communication if this thing will go ahead!! Please, everybody be patient. Thanks to Ilya and the team for updating it...