version number

  • Thread starter Thread starter frazan
  • Start date Start date
F

frazan

Hi, maybe it's a stupid question...
I never have understood the real meaning of software version number,
and when I must change it?
There's some standard, where over Internet, can I find it?
I think something like these examples:
(.net - automatic)1.0.2300.27500(why so big numbers?);
(other) 1.0.18.0, 1.3.1, 1.0a, 1.0b, 0.45 (why zero?)...
depend it from how a person wake up at the morning ? :))

Sorry, but I'm not able to find anything about it.

frazan
 
My understanding of it is as follows:

Version.MajorBuild.MinorBuild.BuildNumber
6 0 1 0

For .Net, the Build # increases each type you run &/or build your project.
Not sure how the other 3 get incremented unless you change it in the
assembly file.
 
..NET's system of version numbers does something like this:

The first two numbers you control.
Out of the box, the third and fourth numbers change every time you do a
build, to differentiate different versions of the exe's / dll's that
you build. However, you can change this behaviour (which you would want
to do if you are selling your software to other people).

In the industry, software versioning usually uses at least two numbers:
the first for major releases and major changes to the system, the
second for releases that introduce minor features or are simply bug
fixes. Companies will keep incrementing the second number until they
feel that something really big has happened to the product (or their
marketing department wants you to think something big has happened) and
then they will move up... say from 2.45 to 3.0.

Versions numbered 0.45, for example, are usually pre-releases of a new
product. The "0" tells you that it's "not quite there yet". The company
or organization will number it 1.0 when they feel that it's a finished
product that they can be proud of. In the meantime, the "0.xx" tells
you "This is still sort of experimental. Use at your own risk."
 
Back
Top