Some manager received a bonus for closing so many bug reports. Wonder if he took the team out for pizza and beers.
Downsized them, rather. Save money on wages too!
Microsoft is closing all old bug reports they couldn't fix
21–23 of 23 posts
Re: Microsoft is closing all old bug reports they couldn't fix
#22At some point, simply keeping track of these things is more overhead than it is worth. I don't work anywhere near the scale of Microsoft, but at some point, you just have to say, alright, we're not fixing this; it works completely different in version N+1 that you should have upgraded to years ago, and btw, we're actually on N+3 now, so we are not going to fix old, janky code that we already fixed.
The bigger issue is that they let it get this bad. In order to get this this point, they would have had to systematically fail triage bugs when they come it, fail to track them as they're fixed, and fail to rectify the problem for over two years. This is an admission that they probably never gave a damn about your bug reports. But hey: if you'd like to help this multibillion dollar company to triage their bugs and re…
Sadly this is not a two year issue, it's been going on for at least the last 10 years. I mainly deal with SQL Server, so maybe it's just particularly bad there - I haven't seen anything to indicate the rest of their products aren't like this to some degree though.
There are active bug reports and feature suggestions for SQL Server that are more than a decade old.
Re: Microsoft is closing all old bug reports they couldn't fix
#23it's interesting to see that Microsoft is actively adopting Jamie Zawinski's CATD model[0].