June 23, 2005

A non-release release -- and what to call it?

Posted at June 23, 2005 03:08 PM in BitWise .

Back in the good old days in 2002 when only a few dozen people were regularly using BitWise, we used to do what I dubbed "slipstream" releases; releases that weren't announced but just silently uploaded to replace an existing release. Such releases usually solved one really obscure problem that most people wouldn't find, but that needed to be fixed before the next version was released.

We now find ourselves at a similar crossroads; there are a few problems with the 1.0.5 release that don't really merit a 1.0.6 release and all of the upgrading that would be required (especially for our business users), but nonetheless need to be fixed. So, for the first time since the 1.0 series started, next week will see the first "non-release release" in a long time.

The new release will be dubbed 1.0.5A or 1.0.5.1 (any preference?) and will address 8 or so non-critical issues. The release will be announced on the web site but will not prompt the new version dialog to appear when logging in to BitWise. This will allow users experiencing one of issues addressed by the release to update, without disturbing those unaffected.

While the complete list of fixes is still being compiled, users running Tiger and users who use non-English characters with logging enabled will most benefit from the update. Stay tuned for more details, and look for this update next week.

Also, don't forget to comment whether you like 1.0.5.1, 1.0.5A or some other notation for the new version! This decision could affect BitWise versioning for years to come, so choose wisely. :)

Comments

I like 1.0.5.1

My 1/2 cent. cheers.

Posted by Sonic_Molson at June 23, 2005 04:50 PM

1.0.5.1

1.0.5A is just confusing and might be incorrectly viewed as an Alpha release.

I say, stick with numbers whenever possible.

Posted by Bryan at June 24, 2005 05:05 AM

Perhaps call it a "hot fix" or "quick fix".

Posted by bobad at June 25, 2005 07:20 AM
Posting of new comments has been disabled for this post.