I've had a frickin' gutsful of Adobe's amateurish and disrespectful approach to dealing with bugs in the bug tracker. I spotted yet another "closed, not enough time" issue today. One which hit me back in 2011. It was first raised in 2009. Five years ago. It first cropped up in CFMX7. It's not a complicated one, it's just that the seem to have a glitch in working with leap years, for some date calculations. "Bug 82249:(Watson Migration Closure)Datediff function does not calculate differences correctly".
This has gotta stop, Adobe.
I checked the bugbase to see how many issues had been closed with "not enough time".
Dating back to 2005.
These are all bugs that have impacted paying clients sufficiently for them to bring them to Adobe's attention. And Adobe's reaction is to just go "oh well... [shrug]... [clicks the 'Close' button]".
This is unacceptable.
So here's what Adobe needs to do. Reopen every single one of them. Then re-triage every single one of them, working out if they are still an issue, or still relevant, or whatever the situation is. Then close the ones that are no longer relevant. And fix the ones that are still an issue. You owe your clients a fair chunk of work here, Adobe.
TBH, I think the ColdFusion team have kinda been defrauding their clients in a way here. They know their product has these bugs, but have chosen to sweep them under the carpet. In a lot of cases they are doubly defrauding their clients because how often have they closed a ticket like this saying "we'll take it up in the next release" It's clear they have no intention of doing this, because they basically don't: there are tickets hanging around for close to ten years!
I also wonder whether the team are misrepresenting the situation to their employers as well? There's currently 515 open bugs (just bugs, not enhancement requests) for ColdFusion, so 349 is like an additional 70% of bugs they are perhaps not disclosing to the people they report to, by surreptitiously closing them.
Secondly to reopening and dealing with these bugs, this approach they have of sweeping issues under the carpet has to stop. If you don't get an issue fixed in time for a release: leave it open. Stop trying to misrepresent the stability of your product by hiding issues.
For the community part, I'm going to do my usual Twitter status update that I do when I publish an article. I'd appreciate it if you're suitably riled by the ColdFusion Team's shoddiness here that you retweet it. I'll embed it here once I've created it.
"Adobe: stop closing #ColdFusion bugs you haven't dealt with" (http://t.co/REIIL5GAHe)We have to work to stop Adobe thinking they can get away with this shit.
— Adam Cameron (@DAC_dev) September 23, 2014
Here is the full list of bugs (colour-coding reflects the bugs' ages):