Help
What we require when you file an issue :
- Add which revision of Trinitycore you're running on (this is the CORE revision, not your client version)
- Add which database, and what revision, you run on
- Add a list of which modifications that has been done to the core (if any)
Example CORE revision number : b1e2cdb905d6a92edeb505eff968d26c453b252b (LAST is not a valid number)
Example DB revision number :
The above is VERY important, so add this when reporting!
For those that wonder what I'm talking about, here's a link to our issuetracker :
http://code.google.c...ore/issues/list
Supplement your crashreports with backtraces - any issues reported as a crashreport and not having a backtrace attached will be deleted on sight.
DO NOT DIRECT-PASTE CRASHDUMPS INTO THE COMMENTARY FIELD - USE ATTACHMENTS OR A PASTEBIN THAT DOES NOT EXPIRE
Please note that you MUST search through the existing issues to avoid duplicate reports - duplicate reports are bad, and you're way better off adding to existing reports if they are of the same type.
Also, for the simplicity of it, when filing reports, use the googlecode tracker when attaching fixes, codesnippets etc.
DO NOT USE PASTEBINS FOR FIXES OR CODESNIPPETS, IT MAKES IT WAY HARDER FOR US TO KEEP TRACK OF YOUR ISSUE/REPORT/SUGGESTION
Attachement requirements :
- Patches : MUST be attached as a file in diff/patch format
- SQL-files : MUST be attached as a file
- Do NOT paste patches/SQL-files into the tracker as regular text in the commentary field
- Make sure the diff/patch uses CORRECT PATHS (no subdir diff of a random directory on your machine)
- When multiple diff/patch/sql-files are involved, or require more than 4-5 files to be uploaded, consider attaching it as an archive ( .zip file )
Also, it seems like certain elements in the community thinks the googlecode issue-tracker is a forum, and attempts to "BUMP" issues. Here's some news to those of you that think so :
The GoogleCode tracker issues CAN NOT be "bumped" - the only thing you do is add noise to the issues you attempt to bump.
In short making it harder for us to actually SEE what a problem might be.
And now some additional information :
- Make sure you are running on the latest revision of the source (we are constantly pushing changes, so your issue might have been resolved already)
- When testing for bugs, make sure you are NOT running a modified core (test without ANY custom patches at all, even if it's just a tiny textchange)
- Don't ask when something will be fixed (it will be sorted as fast as we can, or when someone has the time to look at it)
- Don't claim that your issue is "very important" (every issue is equally important to us - the only exception is when it crashes the core AND have a proper crashdump attached)
- Don't claim that a change "makes function XXX unusable/unplayable" (give a FULL and DETAILED report)
And to make it a little not-so-harsh for those that actually DO understand what the tracker is and use it correctly :
Your feedback is, as always, important to us, and we appreciate the testing and information that you assist us with.
This post has been edited by click: 15 May 2010 - 01:17 AM
