> Today, I've been nattered at by the project's former lead developer over a bug that I
> had already been trying to solve for the past two days, and said same developer
> apparently felt that it would be appropriate to check in a minor change just 12 hours
> before release, despite several people including the current team lead stating that
> it was out of line.
>
are you STILL on about this?
there was a conversation with Micko, over a bug that I thought was a bug in BGFX (not MAME) and surprised me because it only happened in a visual studio debug build. This conversation had nothing to do with you, an alt-enter bug for SDL builds had just been fixed, so it seemed relevant to talk about a crash that happened in that situation while it was fresh.
Once it was established that it was your bug, we decided to leave it to you.
We left it to you because previously when somebody fixed a bug in your code you ended up having a similar tantrum, so it's really not clear what we're meant to do, let you fix the bugs, fix them for you, ignore the fact that MAME crashes on us?
As for the rest, you're raging at me over this? it happens before every release, driver level changes. In this case the work I'm doing is to a minor, "non-working" driver, and has resulted in countless cleanups, which to me is a good thing to be doing before a release. If I have sets to add I typically look at what other improvements I can make too, in this case a driver entirely full of overdumped roms was not something I wanted to make uglier by adding even more, so I tasked myself with cleaning it up.
People claiming I'm breaking rules is ridiculous, the precedent for the changes I made was set almost a year ago, and that was with an actual *working* driver.
Seems people are using anything they can to rage at me lately.
|
Index 
Flat 
Re: I quit
Reply
