Why team don`t use Bugtracker ?!

masaykh

Prince
Joined
Jan 16, 2012
Messages
446
You have bugtracker here : http://sourceforge.net/p/caveman2cosmos/bugs/
But you dont gather bugs nor give such possibility to gamers...i dont understand that...

i see many times how someone ask something and you tell him:"we know about it" or "no one know answer"

But...but it will be easy to track such things and gamers will have opportunity to see if something reported or not!

please reconsider actively using bugtracker
 
I suspect that Koshling was going to teach us about it but we were discovering how to use this new fangled SVN thing and so never go round to it.
 
It is very simple

someone post in tracker all info he\she have, and choose needed (tag\category) like
absent texture \ CTD \ problem with units \ AI
then one of you check bugs and see posted problem you check it and if problem reproduced
you make comments and
1 fix it
2 or give it away to someone more experinced in that problem

Koshling need to open tracker to gamers so we can post there and give modders needed permissions

i suppose that all of team will be need to register in sourceforge
 
It is very simple

someone post in tracker all info he\she have, and choose needed (tag\category) like
absent texture \ CTD \ problem with units \ AI
then one of you check bugs and see posted problem you check it and if problem reproduced
you make comments and
1 fix it
2 or give it away to someone more experinced in that problem

Koshling need to open tracker to gamers so we can post there and give modders needed permissions

i suppose that all of team will be need to register in sourceforge

We already are registered on SF to have SVN commit access.
 
We were introduced to an issue tracker a while back and found any use of a second tool outside of the forum to try to track issues completely failed... we're used to using this I guess. But if someone were to use such a tool to compile and maintain a proper list of all reported bugs and issues and whether they were addressed or not then post the list of loose ends on the bug thread as we enter the debugging phase of the cycle, I'm sure we'd all be more than grateful and more would be addressed and less would be forgotten.
 
Back
Top Bottom