> I'm going to go ahead and guess that the problems discussed
were fixed, and I'm closing this bug report.
If only there was a way to find out, instead of guessing.
I’m going to start trying this at work. I wonder how it will be received?
If only there was a way to find out, instead of guessing.
I’m going to start trying this at work. I wonder how it will be received?
You’ve never done that at work? In every company I’ve worked for, nobody would bat an eyelid at dropping an issue that hasn’t been touched for more than a year
Dont just push code and expect others to point out your flaws. Take some responsibility.
Developers absolutely should be testing for the issues they know about. QA is there to look for unknown issues.
Any company that depends on QA for testing and doesn’t make devs to it is miserable to work for (both as a dev and a QA).
Were all problems fixed? Almost certainly not. Many will have become overcome by events, though. The ones that are still pertinent will reopen.
Such that anytime I see a large percentage of bugs closed like this, this reflects more on working in the ticketing system than it does on fixing the problem it is managing.
They report something. You badger them for six weeks to collect enough information to reproduce it. You fix the problem and slate it into a release and make it available. They don't take the release for another seven months.