Over the weekend I released ColdFire 220.127.116.11. This version works with Firefox 9 and Firebug 1.9. You can download the latest from the new GitHub project site. If you have the current 18.104.22.168 version installed, there is no need to update your server side debugging code as that has not changed with this release.
Changes in the ColdFire Project
There have been some changes to the project with this release, the biggest is the move to GitHub. Moving forward the code will be hosted on GitHub and I will use the GitHub issue tracker to track bugs. The packaged releases can also be downloaded from the GitHub downloads page and I'm hoping to put some documentation up on in a wiki or project page soon.
I'll continue to maintain the RIAForge site, but I've disable the blog, forums, issue tracker.
I'm hoping this move to GitHub will encourage people to contribute to ColdFire.
Why did this release take so long
I know a lot of people have been asking for an updated ColdFire for some time. Some people have even thought the project was dead. Well about that...
As any user of Firefox knows, in the Spring of 2011 Firefox moved to a new rapid release cycle. In order to better keep pace with the Firefox, the Firebug team set about improving the internal architecture of Firebug. Unfortunately this meant that the changes introduced in Firebug 1.8 broke ColdFire. In another interesting Firebug development, right around the same time as the Firebug 1.8 release John J Barton, the lead developer of Firebug for the past several years, left the Firebug Working Group. All of this meant that Firebug 1.8 was a bit of a transitional release. I made a few attempts to get ColdFire working on Firebug 1.8 but ultimately determined a substantial re-write of ColdFire was in order. Rather than building on the Firebug 1.8 release, I decided to wait for Firebug 1.9, which would be the second release on the new internal architecture. Firebug 1.9 was released earlier this month and since then I've been working on the ColdFire update as I've had time.
For a long time I've been against posting ColdFire to the Mozilla Addons site, or AMO, because ColdFire is more than just the Firefox extension; it also requires the ColdFusion debugging templates. However with Firefox's new rapid release cycle I can no longer manually update the extension every time a new Firefox is released so look for the next release of ColdFire to be on AMO.
That's all for now. As always, please report any issues with ColdFire to the new GitHub issue tracker.