> well, while fixing the memleakage is pretty straight forward (when I find a little > time and got my own pc under my fingers...) where should I post reports to when I > find something I myself cannot fix (while the original developer might fix it within > seconds when informed...) > If I post it here, people moan...if I post it at mametesters it gets deleted...I have > to wait a month to be able to post it there...so yes, MAME's way of development ain't > agile...fine...got that....
MAMETesters is about logging known issues and historically, because of its source availability, this has always covered release version only duplicated only using the MAMEDEV produced binaries. Personally, I wouldn't have closed your bug, but suspended it until such time a release came out and then checked to see if it was still valid if confirmed. Right now, there isn't an official place to discuss current GIT development bugs. Since I and other Devs frequent a number of public forums, any of those places (including here) would be a valid place to bring such errors to light, even if MT don't accept them as bugs immediately. That said, that particular bug has not been addressed yes and has been present for nearly 3 weeks now.
If you would like to contribute the codefix, you can send out a DIFF or send a GIT Pull Request with the fix in question. Information is available Here.
MAMEDEV is working on a forum which should become public hopefully in the near future. Along with discussion, we'll have an official place to post/update/monitor current GIT bugs.
|