Solving bugs

[Thalassicus]

Hello!

For anyone curious I'd like to give a quick rundown of how I squash bugs and other problems. I alternate between creative tasks (like designing policies) and technical stuff (solving bugs) to avoid getting burned out. I let the left side of my brain take a vacation while the right half is busy!

I strive to make the game as fun as possible with as few problems as possible. I do my best to reply to each and every bug brought up on the forums. Sometimes it takes a days or weeks to fix a bug, but everything gets my attention once I have the time and energy to address it.

 

[pba]

Would love to know/help. The problem is i didn't really ever find the changelog. Reading through the posts you make lets me have an idea of what you are aware of/what people have already noticed, but a bugtracker would be so awesome instead of the bug posts. Reading the commit statements would help a lot in knowing what you have solved and what is pending.

that being said, i usually am surprised with your speed of addressing stuff whenever i update.

 

[Thalassicus]

I should probably set up an actual bugtracker system... there's probably lots of free ones online.

 

[EmperorFool]

Your projects on Github have built-in issue (bug) trackers, though they require each user to create a free account. The nice thing about using these is that they tie into the commits. You can reference issues in your commit messages and vice versa.

A separate free hosted solution is Fogbugs. I have never used it, but I have used other software from Fog Creek Software. They are a top notch development shop so I figure their bug tracker is probably quite good. It has no integration with Git according to that page, but perhaps it's just an oversight. I assume it allows anonymous reporting given the description of its features on that same page.

You could also create a project at SourceForge and use it only for bug tracking. It's also free and allows anonymous reporting.