Mozilla Firebird 0.7.1 Released for Mac OS X

Sunday October 26th, 2003

A minor update to Mozilla Firebird 0.7 has been released for Mac OS X users. Version 0.7.1 is a recommended upgrade that fixes several usability issues and significantly improves performance. The Mozilla Firebird 0.7.1 Release Notes have more information. The new build is available for Mac OS X only from Starting with version 0.8, Mozilla Firebird will use Kevin Gerich's Pinstripe as the default theme on OS X. This theme is also available for 0.7.1.

In related news, the Mozilla Firebird Roadmap has been updated with details about the the plans for each milestone up to 1.0. The Mozilla Firebird 1.0 Charter has more general information about the project's goals.

#30 It might look dumb the way you did it...

by adipose

Wednesday October 29th, 2003 1:02 AM

You are replying to this message

But if you show the whole picture:

.6, .6.1, .6.2, .7, .7.1, .8, .9, .10, .11.1, 1.0, 1.0.1, 1.0.5, 1.1.1, etc...

The numbers aren't true decimals, as someone else already pointed out. They are versions and sub versions. A program reaches 1.0 when it's ready for production, not before (at least it's supposed to work this way). But you still release major milestones when major things are accomplished.

Perhaps the .10 and .11 ruin your notion of a decimal system, but it wasn't ever a decimal anyway--it was versions, sub-versions, and sub-sub-versions.

Other problems with your system would be when a product goes from 1.x to 2.x. Must a program reach 1.9 before going to 2.0? Or is it ok to jump from 1.4 to 2.0? The answer is: yes, because the change from 1.x to 2.x represents major (and usually incompatible) changes, not .1 greater than 1.9. Also, if a program reaches .9, there will probably be excessive sub-versions if the program is deemed not ready for 1.0: .9.7, .9.8, .9.9, .9.9.1, .9.9.2, which starts to get ridiculous, especially if the changes are bigger than those numbers would imply.

There is no reason to impose the arbitrary base of 10 to a versioning system just because we use base 10 in our daily lives. While I agree it is nice to know that .9 = product almost finished, and .5 = product half done, the truth is versioning never really works that way, because the developers can't really predict when a product will be finished. Frequently products get bogged down in the .9xxx as I described above, specifically because they try to follow a decimal type system, even though development doesn't mirror that.

The choice to use .10, .11, .12 was made after it became clear Fb was progressing through milestones faster than it was approaching 1.0 status, and I think it was the right decision. It might look a little strange, but at least the system will be consistent, isntead of progressing towards 1.0 and suddenly halting.