> > > I know that, it's just I wanted to show this problem. > > > > What do you feel the difference is between "THIS GAME DOESN'T WORK" and the game, > you > > know, not working that you wanted to report? > > I think sometimes people get upset when a non working game starts not working in a > different way than it did before. Sometimes a non working game appears to sort of be > working at some point, but nobody tries to maintain that state because the game is > marked as not working. > > We should probably have a bug open on mametesters for each game that is marked as not > working and describe what it does. Maybe have them marked differently (low priority > etc)
I already do this for non-working games which have experienced "heavy" regression, such as completely missing audio/video or an assert/crash that never showed before provided I can find a breaking revision.
There is sort of a list at mamedev.org in the wiki showing why not working games are labeled as such which should help: http://www.mamedev.org/devwiki/index.php?title=GNW
|