How should program versions be numbered?

[Flying-Kiwi]

Hi,

I'm ready to release a beta version of my program. What's the convention for numbering beta's and 'release' versions?

In fact, since this is the first tryout, should it be labelled as 'Alpha'?

Thx

[DragonQ]

Usually, like this:

Major.Minor.Revision.

For example, if it is your first major release, but released a small patch and then you fixed some bugs in it, it'd probably be like this:

1.1.1

I prefer to use letter for the revision, but VB.NET will not allow you to do this (although you can have an "About..." section in your program where you can put in any version number you like - e.g. 1.0a).

For Aplha releases, I suggest using 0.x.y (where x is a number between 1 and 4, and y is the revision number which you can change whenever), and for Beta, you could use 0.a.b (where a is a number between 5 and 9 and b is the revision number which you can change whenever).

[Kasracer]

Most places go by 3 sets of numbers. Example 1.2.7

The first number being a major release (like once it's finished beta testing and features are finalized and polished. Also should be stable). The second number is usually for added features that don't require a completely new version. The 3rd is usually for bug fixes and such.

Most BETAs and ALPHAs are usually a pre major version release (like .25 for example).

Though you can follow your own number scheme. There isn't anything wrong with that. .Net has a built in scehem similiar to the one I described (though I don't know if it's quite the same).

Betas are usually for programs that are fairly complete and fairly stable but work still needs to be done. Alphas are usually programs with quite a lot of features needing to be added with experimental things and sometimes are instable.

[Flying-Kiwi]

Thx for the replies.

Just to be clear, how is an Alpha and Beta version written?

As "Alpha..."?

Also, how do you get VB to number versions?

Thx again

[jmcilhinney]

Also, how do you get VB to number versions?

You use the AssemblyInfo.vb file.

How you number your versions is completely up to you. Many people would use 0 as the major version number for prerelease versions of a new product, but once you release version 1.0, how do you number prerelease versions of a 2.0 product? I prefer to number all versions of my first release 1.0 and then vary the build and revision numbers. If a build is a beta I simply add "Beta" in the about box and perhaps the window title. VB.NET supports conditional compilation so it is quite easy to declare a BETA constant and have things like Labels or forms diplay different Text for beta versions. Personally, I increment the major version number if I upgrade the functionality considerably, the minor version number if I upgrade the functionality only a little, the build number if I make a change or fix that alters what the user sees or how they interact with the app, or the revision number if I make a change or fix that is invisible to the user.