08-31-2009, 08:46 PM
When it comes to bug reporting, there are several imporant steps that can help us to fix the bug.
First of all, it comes to the player who finds a bug. At the moment, we make players create topics on mantis, however, since we're moving to trac, we have to change this way.
I've noticed a lot of people didn't bugreport anymore since we've switched to mantis bugreporting. That is why I think it is better we re-introduce forum topics. We can easily discuss there too, and other players can tell when they've encountered the bug.
We then determine if a bug is really a bug, and when the bug exactly occurs.
We can then create a ticket on trac. This ticket should have an exact description of the problem. It should tell what it is, when it happens, and who found it. We will also need to add a priority to the bug, and a target build of the gamemode.
Most bugs should be fixed within a week, so usually you can just use next sunday's build, however it might happen the bug gets reported on sunday and can't be fixed anymore, in that case, the bug should be fixed in the build of the next week. We will also give priorities to bugs, how fast should a bug be fixed, would it require an immediate restart or not? This all should be chosen by the priority. Trac offers 5 priorities: Blocker, critical, major, minor and trivial. We can still change those though. I would suggest Critical for gamemodecrashing things, which need an update as soon as it is fixed. Major should be fixed in next sunday's update, and is for really annoying bugs, minor is for smaller bug which still annoy people, trivial is for only really small bugs, that won't need very fast fixing, but need fixing some day. After that the ticket can be posted, and a devver can assign it to himself, usually within a day.
For fixing bugs, you will need the details from the bugreport, and you will have to find out where something could be wrong, change stuff there, try to find a bug there. Some bugs require some debugging, this usually can be done easily, by adding debug statements, and testing it on the testserver. If you would need a fully crowded server tho, you can commit the debug statements, and make sure everythings gets saved in a .txt, so the bug can be found.
After you think you've fixed a bug, you can start testing it. This should be done by testing every single case where it occurs, especially the parts the bugreported described. When you're sure everything has been fixed, you can commit your code, and set a bug to fixed.
Any comments on this? Post them here within 5 days.
First of all, it comes to the player who finds a bug. At the moment, we make players create topics on mantis, however, since we're moving to trac, we have to change this way.
I've noticed a lot of people didn't bugreport anymore since we've switched to mantis bugreporting. That is why I think it is better we re-introduce forum topics. We can easily discuss there too, and other players can tell when they've encountered the bug.
We then determine if a bug is really a bug, and when the bug exactly occurs.
We can then create a ticket on trac. This ticket should have an exact description of the problem. It should tell what it is, when it happens, and who found it. We will also need to add a priority to the bug, and a target build of the gamemode.
Most bugs should be fixed within a week, so usually you can just use next sunday's build, however it might happen the bug gets reported on sunday and can't be fixed anymore, in that case, the bug should be fixed in the build of the next week. We will also give priorities to bugs, how fast should a bug be fixed, would it require an immediate restart or not? This all should be chosen by the priority. Trac offers 5 priorities: Blocker, critical, major, minor and trivial. We can still change those though. I would suggest Critical for gamemodecrashing things, which need an update as soon as it is fixed. Major should be fixed in next sunday's update, and is for really annoying bugs, minor is for smaller bug which still annoy people, trivial is for only really small bugs, that won't need very fast fixing, but need fixing some day. After that the ticket can be posted, and a devver can assign it to himself, usually within a day.
For fixing bugs, you will need the details from the bugreport, and you will have to find out where something could be wrong, change stuff there, try to find a bug there. Some bugs require some debugging, this usually can be done easily, by adding debug statements, and testing it on the testserver. If you would need a fully crowded server tho, you can commit the debug statements, and make sure everythings gets saved in a .txt, so the bug can be found.
After you think you've fixed a bug, you can start testing it. This should be done by testing every single case where it occurs, especially the parts the bugreported described. When you're sure everything has been fixed, you can commit your code, and set a bug to fixed.
Any comments on this? Post them here within 5 days.
It was better when it had two child boards: Purged and Resolved. That way we can check if any outstanding bugs are there which have not got a ticket or haven't been fixed yet.