Fulqrum Publishing Home   |   Register   |   Today Posts   |   Members   |   UserCP   |   Calendar   |   Search   |   FAQ

Go Back   Official Fulqrum Publishing forum > Fulqrum Publishing > IL-2 Sturmovik: Cliffs of Dover > Technical threads

Technical threads All discussions about technical issues

Closed Thread
 
Thread Tools Display Modes
  #1  
Old 04-04-2012, 08:54 AM
Ataros Ataros is offline
Approved Member
 
Join Date: Jun 2010
Location: USSR
Posts: 2,439
Default

Quote:
Originally Posted by FG28_Kodiak View Post
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.
  #2  
Old 04-04-2012, 09:00 AM
FG28_Kodiak FG28_Kodiak is offline
Approved Member
 
Join Date: Dec 2009
Location: Swabia->Bavaria->Germany
Posts: 884
Default

Ok registered
  #3  
Old 04-04-2012, 09:02 AM
ZG15_FALKE ZG15_FALKE is offline
Approved Member
 
Join Date: Sep 2011
Posts: 19
Default

I would trie, no experience in voting system though.
  #4  
Old 04-04-2012, 09:09 AM
Ataros Ataros is offline
Approved Member
 
Join Date: Jun 2010
Location: USSR
Posts: 2,439
Default

Got an e-mail from luthier:

Quote:
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"
  #5  
Old 04-04-2012, 09:11 AM
Dano Dano is offline
Approved Member
 
Join Date: Oct 2007
Location: Petersfield UK
Posts: 1,107
Default

Excellent stuff, my thanks to all involved
__________________
i5 2500k - Asus P8P67Pro - Crucial M4 64GB - 8GB DDR3 - Geforce Ti 560 1GB - Xonar DG - W7 X64 SP1

Last edited by Dano; 04-04-2012 at 09:21 AM.
  #6  
Old 04-04-2012, 09:24 AM
41Sqn_Banks 41Sqn_Banks is offline
Approved Member
 
Join Date: Oct 2007
Posts: 644
Default

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.
  #7  
Old 04-04-2012, 09:33 AM
Ataros Ataros is offline
Approved Member
 
Join Date: Jun 2010
Location: USSR
Posts: 2,439
Default

Quote:
Originally Posted by 41Sqn_Banks View Post
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.
  #8  
Old 04-04-2012, 10:42 AM
SG1_Lud's Avatar
SG1_Lud SG1_Lud is offline
Approved Member
 
Join Date: Jul 2010
Location: Spain
Posts: 376
Default

Quote:
Originally Posted by 41Sqn_Banks View Post
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
  #9  
Old 04-04-2012, 02:29 PM
mazex's Avatar
mazex mazex is offline
Approved Member
 
Join Date: Oct 2007
Location: Sweden
Posts: 1,342
Default

Quote:
Originally Posted by 41Sqn_Banks View Post
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
__________________
i7 2600k @ 4.5 | GTX580 1.5GB (latest drivers) | P8Z77-V Pro MB | 8GB DDR3 1600 Mhz | SSD (OS) + Raptor 150 (Games) + 1TB WD (Extra) | X-Fi Fatality Pro (PCI) | Windows 7 x64 | TrackIR 4 | G940 Hotas
  #10  
Old 04-04-2012, 09:13 AM
albx albx is offline
Approved Member
 
Join Date: Jun 2010
Location: Italy
Posts: 716
Default

Quote:
Originally Posted by Ataros View Post
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...
__________________
AMD Phenom II X4 965BE OC@3.8ghz
DDR3 G.Skill eco 4gb
ATI Asus EAH6950 2GB shaders unlocked
Asus Xonar DX
Asrock 870 extreme3
Windows7 x64 Ultimate
Saitek X52pro (stick modded) - Saitek rudder pedals - SteelSeries Siberia V2 headset
Freetrack ps3eye
Samsung 23" SyncMaster XL2370
Closed Thread


Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 02:43 PM.


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