Community bugtracker is up @ il2bugtracker.com

[Ataros]

Originally Posted by FG28_Kodiak

Made it sense to post bugs before the next patch is out? May be some of them are (hopefully) already fixed.

I think it is better to test it now to make sure it works when the patch is ready. Maybe we manage to make luthier to officially announce it in the patch thread too if it works. We still need to configure some plugins, get more admins, etc.

[FG28_Kodiak]

Ok registered

[ZG15_FALKE]

I would trie, no experience in voting system though.

[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

[mazex]

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

+ 1

[albx]

Originally Posted by Ataros

Got an e-mail from luthier:



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"

good.. but we can change it anytime if another system can be suggested...