Bugtracker Developers Guide

This page is still work-in-progress and its content open to discussion!

These are some instructions for developers about how to use our github bugtracker.

Generally, bug labels (these funny colored things) can't be set by normal users, only by developers. This is a little guide what they mean and when to set them:

Label name	Description
bug	Two meanings: the bug is accepted/confirmed by a developer, and it's only correcting an existing error, not adding a new game feature
enhancement	Two meanings: the issue is accepted by the development team (just ask about it in IRC), and it's adding new game features, not only correcting bugs
upstream	The upstream labels are for marking bugs that have to be fixed in the mana client/server instead of just changing game data. They should contain a link to a manasource bug report.
website	Changes on the website have to be made (content, wiki, worldmap, ...)
duplicate	Self explaining, use when the bug is a duplicate of another one (specifying which bug is duplicated)
invalid	Bug report can't be confirmed/reproduced, so we don't take any action on it
mapping	All mapping (changing tmx map files) related bugs
question	Whenever a question is filed in the bug tracker (mostly by users) - they should be closed after some inactivity though (or after solving the question of course)
wontfix	Either an enhancement we don't want to implement or anything that is expected behaviour