Monday, May 28, 2007

Proper Use: Alpha/Beta

I'm being deluged with offers to participate in "Beta" versions of (mainly email) applications, and they're coming to give me the shits. See, a "beta" version is something that's not yet ready for full release, it's.. well, let me just copy and paste:


"Alpha" is a version tested (used) by people who also designed/implemented it. "Beta" is a version tested by people who didn't design/test it, unless perhaps the design/test team did get them to produce and/or review acceptance tests/criteria. And "Release" is the version that has been tested OK against release criteria.

To be complete, correct version numbering isn't very subjective, either. The format is >major<.>minor<.>patch< . Bugfixes (not new features) increment the "patch" number. Format changes, in API, transmission (eg. network) or storage (eg. files) still backwards compatible increment the minor number. Feature changes still using the same UI increment the minor number. Format changes not backwards compatible, feature changes which change the UI, or transformational bugfixes which change either formats or UI to break backwards compatibility all increment the major number. Incremental builds can extend the numbers with a dash (eg. "2.13b4.77-154", for the 154th build of the 77th bugfix of the 4th beta of version 2.13), but only in Alpha and Beta versions, not actual releases. A good project's bug reporting will list bugs by their reported ID in lists of which bugfix release fixes them. "Release Candidate" numbers are just nicknames for the last in the series of Betas. Much as the the b1 version is identical to the last Alpha version.

That's it. Each number change should have an Alpha/Beta/Release version, though Alphas can sometimes be skipped with tiny bugfixes. So there's no need for "odd/even" version numbering to reflect "development" versions. And numbers are sequential, except of course when a higher order number increments, resetting the smaller order number (eg. 2.13.77 -> 2.14.0 ->2.14.1). Version numbers have been hijacked by marketdroids, which just confuses the market they bamboozle, which is ultimately bad for sales, and even worse for costs of support. The version number should tell people whether to upgrade, and whether their old data, training and related activities will be noticeably impacted (with associated extra costs).

Netscape broke everything with it's "public Beta" release that defined Web SW distribution. Microsoft has made the curse ubiquitous with SW versions 1, 2, 3 standing in for Alpha, Beta, Release, but mixing it up with new features to substitute for bugfixes. And Service Pack versions that form an entire new chain, and ongoing patches, and every other unmanageable version numbering "scheme" possible. And Linux distros continue the damage with the odd/even numbering and arbitrary versioning, with major releases measured in minor numbers, requiring various extra versions, and version numbering of each release for each distro.

But the numbering schemes change monthly, quarterly. If developers just return to the simple discipline, we'll get back to numbers that actually mean something helpful to users and developers, not just marketdroids counting up to their next bonus."


Source

No comments: