Effective this release (0.146), all regressions in any official source release of MESS should be verified and reported to MAMETesters. This has come about due to the old bug tracking system, BugZilla, being lost in a server crash and wipe. Since MAME has many of the same core parts and interfaces, it made sense to modify MANTIS (current MT bug reporting software for MAME) to also allow handling for MESS bugs.
Please refer to the site for a full rundown on what is or is not a valid bug to report. You can get this information on site by selection "Help" from the top menu bar.
Some basic rules for submissions:
1) When signing up for a MAMETesters account, you are not instantly a TESTER, but a VIEWER. Moderators and Administrators will, when they are able, research your signup data to make sure you check out. If given the "all clear", your status will change to TESTER shortly thereafter and can report your bug(s) to the database. This is a one time delay to stop spammers and bots and is required.
2) MESS/SDLMESS command-line builds are the only means to verify ANY bug before reporting. Using MESSUI or any other intergrated MAME/MESS combo builds such as (UME) are not valid for testing and should not be used in proving your posted bug exists.
3) Report bugs only if you have proof of regression or breakage from one official release to another. If you happen to build or download a SVN or GIT version that lies in between official releases and notice breakage, you must bring it up to the MESS Forum for discussion and fixing before the next official release.
4) Take your time and fill out all required/applicable fields. Use the tutorial and [?] links to help determine what is valid input. Be concise on what the bug is, how you duplicate it (procedures) and if you know when it last worked as expected.
MAMETesters: http://mametesters.org
MESS Forum: http://forums.bannister.org/ubbthreads.php?ubb=postlist&Board=1
|
Index 
Flat 
Bug Reporting for MESS
Reply
