Note: This blog post is from 2015. Some content may be outdated--though not necessarily. Same with links and subsequent comments from myself or others. Corrections are welcome, in the comments. And I may revise the content as necessary.If you'd not noticed, the CF team has been busy fixin' bugs! Over 300 in CF11 in just the past month. Check out these two announcements today of prereleases of update 5 for CF11 and update 16 for CF10:
- ColdFusion 11 Update 5 prerelease build now available
- ColdFusion 10 Update 16 prerelease build available
This is on top of the release earlier this week of the final version of CF11 Update 4 (which had been in prerelease for a couple of weeks):
Great to see the CF team cranking on the bug fixes. I count just under 120 in the technotes for CF11 update 5, and just under 40 in CF10 update 16. And there were just under 200 fixes in Update 3 of CF11, which again was released just in recent weeks.
Yeah, but what about all those bugs?
Yes, I know some could twist things and say "yeah, but the problem is that there are so many bugs to be fixed". Sure.
Still, for others who may have longed to see their bugs fixed,
here's hoping that these or any of the other recent updates may address those for them.
File your bugs, vote for others
And let this be a lesson to folks: if you've got a problem, don't just publicly complain about it. File a bug report. That said, since the team does need to triage bug fixes and does take votes into account, some may want to publicize their particular bug to garner interest in it.
But please: don't ask me to do that for you here. :-) You may notice I don't even do that myself here for bugs I report. I trust that the system works and important problems will be found and voted upon by folks.
The recent spurt of bug fixes, as well as some specific responses to issues I've raised (some, not all), does give me hope that the process is working.
Do remove any prerelease updates when things go final
Oh, and if you may have applied (or will apply) one of the prereleases, don't forget to uninstall it when the final comes out. And change your CF Admin "update settings" page to point back to the original URL (versus the prerelease update feed URL). Use the provided "restore default URL" for that. In fact, I'd recommend you do that right after downloading a prerelease, so you don't forget.
Sadly, I have found that even with the default URL restored, we are NOT notified that a new final release is ready if we have the prerelease installed. That's unfortuante. Until that may be fixed, do keep an eye on that CF team blog above. It's a great resource of what's going on with CF.
For more content like this from Charlie Arehart:
Need more help with problems?
- Signup to get his blog posts by email:
- Follow his blog RSS feed
- View the rest of his blog posts
- View his blog posts on the Adobe CF portal
- If you may prefer direct help, rather than digging around here/elsewhere or via comments, he can help via his online consulting services
- See that page for more on how he can help a) over the web, safely and securely, b) usually very quickly, c) teaching you along the way, and d) with satisfaction guaranteed