Version numbers

[mattalexx]

What is the exact meaning of the major and minor numbers in a software version specification? For example, say I wrote MyProgram v1.0 and had just updated it. Should it be v1.1 now? or should it be v2.0?

What does it all mean?

Just something I've always wondered about,
Matt(+)

[JungleMan]

If it's a major change to the way the software works, do 2.0

If it's a few added features and bugfixes do 1.1

If it's just a couple of bugfixes do 1.0.1

I think that's pretty much how it works :)

[Cander]

I have never seen any actual rules for this, but usually I go by

Major 1.*.* - Any big changes with a new interface or big changes to said interface or even a big re-write

Minor *.1.* - Perhaps no changes of any major scale to aany existing fuinctionailty but some new functions in the program

Revision *.*.1 - Small bugfixes to existing functions.

[mattalexx]

oh, ok..

I thought it was more official than that. :D

Anyone else have anything to add?

[Gimlin]

I got a question Why do they always skip numbers some times??? Like you see some software that 5.43 then next one is 6.03 ***?

[JoshT]

Some people use even/odd minor versions to specify a stable or a development release.

[nabeels786]

that and sometimes like where i work they'll have a few builds in between and change the version, and by the time they release it, its skipped a few version numbers

[jim mcnamara]

Try Oracle

They used make releases almost every week back in the early 80's.

We run 8.1.7.3.0

Talk about granularity....

[JoshT]

Originally posted by jim mcnamara
Try Oracle

They used make releases almost every week back in the early 80's.

We run 8.1.7.3.0

Talk about granularity....

Wasn't the original version 2.0 because they didn't want to sell a 1.0 product?