Version Number Format

[Radsam]

Hi,

Is there a standard that developers use when setting version numbers? I often see a version number with the following format "#.#.#.#". Could someone explain how this is used or point me in the right direction.

Thanks

[Blue_Drache]

Hi,

Is there a standard that developers use when setting version numbers? I often see a version number with the following format "#.#.#.#". Could someone explain how this is used or point me in the right direction.

Thanks

<{POST_SNAPBACK}>

I think it's something like version.edition.???.build#

I just don't know what the third one is.

Version# changes = major code change

edition# changes = bugfix/minor code tweak

???# changes = ???

build# changes = used mainly for betas, code additions, tweaks, etc....

Edit: Spelling errors corrected.

Edited March 16, 2005 by Blue_Drache

[Kerberuz]

Hi,

Is there a standard that developers use when setting version numbers? I often see a version number with the following format "#.#.#.#". Could someone explain how this is used or point me in the right direction.

Thanks

<{POST_SNAPBACK}>

It's my understanding that version number follow this format major.minor.build

I'm not aware of a fourth item, not saying there can't be one though.

[jpm]

version.major.minor.build

minor can be not so minor but not as high as major. that's the reason when we switch from 3.0.102 to 3.1.0

You can ignore the build number which is mainly use during beta phase

[Blue_Drache]

version.major.minor.build

minor can be not so minor but not as high as major. that's the reason when we switch from 3.0.102 to 3.1.0

You can ignore the build number which is mainly use during beta phase

<{POST_SNAPBACK}>

I was close. Thanks for waking up long enough to educate us.

Now go back to sleep.

[zcoacoaz]

now my program versions will have common sense.