HowTo: Submit a bug report
From Team UMX Wiki
If you stumbled across an anomaly or an error we would like to encourage you to let us know about it. As the developers, resources and available time of the members of Team UMX are limited it can always happen that we oversee an error or an unwated behaviour. This is why we need you to take action when you come across something unusual. This guide will help you provide Team UMX with the needed information to get the problem solved as soon as possible.
Contents |
Has this bug already been reported?
Before you ever post a bug report in our forums and/or Trac please make sure that it is something new that noone has encountered and posted yet. Duplicate reports will simply be ignored and deleted as it would takes us more time to answer the same questions over and over again than you using the search functionality of our forums and our Trac before posting the bug. We do not want to keep anyone from posting a bug at all as we are very greatful for every report we get but it spares everyone some time if you first take a look at what has already been reported. Maybe your problem has already been solved and there is a way to fix it.
Congratulations! You're the first to discover this bug. But what now?
I'm absolutely positive that this is a bug!
Could be a bug, could be a misconfiguration...!?!?
Where do I post a new bug report?
How do I post a new bug report?
The holy debug log
Screenshots and other pieces of proof
Whenever you discover a bug which can be caught on a screenshot please try to provide one (or more if necessary) to help us in locating the problem faster. Also provide a description on what we should see on the screenshot and what the problem is (if it is not all too obvious).
How do we reproduce it?
If the bug is something that happens/appears only under certain conditions and you have found out what to do to force the bug please provide a detailed step-by-step description on what we must do to notice the bug you found. Every detail (special configuration settings e.g.) can help identify the problem. The more accurate your description is the faster we can solve the problem.
How should I proceed if I'd like to try and fix the bug myself?
As the time of every developer of Team UMX is limited we always welcome if other people try to hunt down and solve a bug themselves. If you plan on solving a bug take a look at HowTo:_Help_develop_UMM. If you have any more questions e.g. where the best starting point for a certain bug is post your goal and your problem in our forums and someone well be happy to provide you with some instructions on what you should do first and where you should start. If you however have already fixed the bug go to our Trac and check if there already is a bug report ticket for it. If you find one post your changes as a Unified SVN Diff (also called Patch). If there is no matching bug report ticket just create a new patch ticket providing information about the bug and how you solved it alongside with the Unified Diff of your changes. Please make sure that you take the Unified Diff from the latest SVN revision to minimize our work on getting your changes into our code.
