Official Fulqrum Publishing forum
Page 7 of 16 « First 56 7 89 Last »
Show 100 post(s) from this thread on one page

Official Fulqrum Publishing forum (http://forum.fulqrumpublishing.com/index.php)
-   Technical threads (http://forum.fulqrumpublishing.com/forumdisplay.php?f=191)
-   -   Community bugtracker is up @ il2bugtracker.com (http://forum.fulqrumpublishing.com/showthread.php?t=30906)

41Sqn_Banks 04-04-2012 02:09 PM
You can also stalk luthiers profile to see his activities

mazex 04-04-2012 02:25 PM
Big Kudos for putting this up... It has been needed for a long time and what is needed to get it working is voluntary admins that reject duplicates and do a quality check before accepting the bugs if they are not filled in properly with steps to reproduce, system specifications and other details needed for the developers according to rules regarding how to file bugs... Otherwise Luthier will get tired of this very fast...

I have not worked with redmine, is it possible to add custom mandatory fields like "Describe background / Steps to reproduce / Your detailed system specifications" etc?

EDIT:

Here is how to set up custom mandatory fields in Redmine:

http://www.redmine.org/projects/redm...neCustomFields

mazex 04-04-2012 02:29 PM
Quote:
Originally Posted by 41Sqn_Banks (Post 405675)
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

Ataros 04-04-2012 02:33 PM
Quote:
Originally Posted by mazex (Post 405785)
Big Kudos for putting this up... It has been needed for a long time and what is needed to get it working is voluntary admins that reject duplicates and do a quality check before accepting the bugs if they are not filled in properly with steps to reproduce, system specifications and other details needed for the developers according to rules regarding how to file bugs... Otherwise Luthier will get tired of this very fast...
Could you become an admin please?

Ataros 04-04-2012 02:38 PM
Quote:
Originally Posted by ZG15_FALKE (Post 405742)
I would suggest one project per released version and correspondingly named. Makes it easier to keep trrack for which version/bugfix the bug or feature was reported/requested.
Then unfixed bugs have to be imported from the old project to the new one or not? It may become confusing for the devs to keep track of 3-4 projects.

Dev-heaven has a separate column for version #. Maybe they configured it somehow? https://dev-heaven.net/projects/cis/issues?query_id=30
Proposals for future are marked as NEXT GEN version.

Strike 04-04-2012 02:42 PM
Finally guys!

Excellent!

I've been promoting this type of communication myself earlier. I have a lot of good impressions from it by playing ARMA 2 and using the dev-heaven tracker :)

Will start registering well-documented bugs in the future. Youtube/printscreen are our friends :)

SG1_Lud 04-04-2012 02:47 PM
Quote:
Originally Posted by Strike (Post 405793)
Finally guys!

Excellent!

I've been promoting this type of communication myself earlier. I have a lot of good impressions from it by playing ARMA 2 and using the dev-heaven tracker :)

Will start registering well-documented bugs in the future. Youtube/printscreen are our friends :)
Long time no post mate. Really, I thought of you when I saw this and recalled how you promote the idea. But finally is here and with the devs involved. Good times.

mazex 04-04-2012 02:51 PM
Quote:
Originally Posted by Ataros (Post 405789)
Could you become an admin please?
Absolutely... We need some admin "forum" to set up the guidelines and policy's of the desired work flow for the bug reporting too.

FG28_Kodiak 04-04-2012 02:55 PM
Quote:
Originally Posted by Ataros (Post 405791)
Then unfixed bugs have to be imported from the old project to the new one or not? It may become confusing for the devs to keep track of 3-4 projects.

Dev-heaven has a separate column for version #. Maybe they configured it somehow? https://dev-heaven.net/projects/cis/issues?query_id=30
Proposals for future are marked as NEXT GEN version.
Added the column "Zielversion" may be the translation is target version.

41Sqn_Banks 04-04-2012 02:56 PM
Quote:
Originally Posted by Ataros (Post 405791)
Then unfixed bugs have to be imported from the old project to the new one or not? It may become confusing for the devs to keep track of 3-4 projects.

Dev-heaven has a separate column for version #. Maybe they configured it somehow? https://dev-heaven.net/projects/cis/issues?query_id=30
Proposals for future are marked as NEXT GEN version.
I've created a version (1.05.xxx), issues can now be assigned to this "target version", however my impression is normally used to define the version that should fix the issue. Maybe we can misuse is to define the version where the issue occurred?


All times are GMT. The time now is 09:11 AM.
Page 7 of 16 « First 56 7 89 Last »
Show 100 post(s) from this thread on one page

Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.