Joe has just released a update to the recent 1.0 release of Firefox Firebug extension.

Changes are:

1. Support escaping the % sign in console.log() calls using %%
2. Support “Find Next” in the CSS tab
3. Fixed problem causing inconsistent breakpoint triggering
4. Deleting a disabled CSS property will work properly
5. Fixed bug that prevented editing of DOM properties with numeric values
6. Inserted warning about incompatibility with Sothink SWF Catcher extension
7. Fixed incompatibility with HTML Validator extension

If you haven’t gotten the update in Firefox yet, go get it now over at Firebug.com

Related post:
Firebug 1.0 Official Release

Tate Needham over at VSoft Technologies hit the nail on the head with a post: “Who cares if the build is broken?”

“If the development team is serious about creating quality software, then the entire team should care about the build being broken. Even if the team does not use any sort of continuous integration practices, a broken build is never a good thing.”

I know I have seen it time and time again when a team gets buy in by say 90% of the team and everything is going great. But then there is that one day when the other 10% of the team thinks automated builds are a waste of time and money. Those are the folks that ignore the emails about the build being broken. Better yet, they are the folks that yell from the mountain top the WOMB (works on my box) mantra.

“Oh I have to check in the library too for the build to work!”

Playing dumb on a development team never really pays off now does it!

It was based on the write up by Derick over at AvacodoSoftware.com: The Build Is Broken… Who Cares?