Firefox 3 developers are taking all the time that they need to accomplish their new Firefox. After the Beta 1 Mozilla has released Firefox 3 beta 2 to get more feedbacks about bugs from its testing community. Bugzilla was a little bit busy lately since the beta 1 thousands of bugs fortunately 900 of them are fixed. Firefox developers are trying to reveal more bugs to make their Firefox 3 better. The Beta 2 features are very promising and the Firefox 3 will definitely beat all competitors.

In an effort to increase the level of Firefox’s visual and interactive polish, I’ll be posting a list of around 7 bugs every monday from now until we finish up Firefox 3.1. These bugs will involve fixing some rough areas of Firefox 3’s UI, landing icons that we meant to land before shipping, and trying to make sure every last pixel is perfect.

Mozilla will fix just 20% of the bugs now in Firefox 3.0 before the final version is released next year, the open-source developer's Web site revealed.

Mozilla plans to release a patched version of its latest browser, to be named Firefox 3.5.1, in response to certain bugs that have revealed themselves following Firefox 3.5's June 30 release.

The object of this post is to make you think about ways we could improve each one. I’ll try to link to bugs where there are bugs, but a lot of these are quite new design decisions only present in 10.04 and hence don’t have bugs filed.

I have been reading this article over at Information Week over and over the past few days because it bugs me. It bugs me for several reasons, the most important reason being that part of it is right.

kde respects bugs. bugs in kde3 have their equivalent in kde4. rule of thumb in developing kde is 'we do not fix bugs. ever.' the worst part is that important bugs in kde3 were not fixed in several years.

Mozilla has pushed out a new version of Firefox that fixes a number of security bugs, including a high-profile bug involving launching Firefox from Internet Explorer.

Finding bugs in your code can be quite nasty—especially if you don’t know where to look. However, finding bugs automatically does not require astronaut training. I think it’s time to leave that “pleasure” to free (as in freedom) automatic static code review tools like the ones reviewed in this series of articles.