When Updating A Program How Do You Determine Versions

[Snapy1]

How do you determine which version to update your program to, its its at v1.0 stage, do you update it to v.1.0, 1.01. How do you determine that?

[Ciccioo]

flip a coin

[defunkt]

Update it to the highest number.

[linusforsell]

In many cases, the updated version number reflects the size or significance of the update.

 

An update from 1.0 to 2.0 would mean it's a big or very significant update, while an update from 1.0.1 to 1.0.2 would mean a smaller and less significant update, 1.0.0.1 to 1.0.0.2 would usually represent an even smaller update. Once a number to the left of another has been changed, all the numbers to the right should be reset to 0 — 1.0.2.5 could for example go to 1.1.0.0.

 

Ultimately though, it's completely up to the developer how he or she would like to number the versions, just make sure to be consistent with the version numbers so that it can be tracked.

[roberto++]

1.01 is higher than 1.0 so typically you would go with the 1.01

 

if you need to know, look for the change log file. this is where the developer will make notes as to the changes from each version. sometimes also called version history.

[zinton]

Find the "about" option 

[WanderingFool]

Oh, one thing to do is something like v1.0 to v1.01 should actually be written as v1.00 to v1.01.  The reason being, if you happen to every have an alphabetical order 1.11 would come before 1.2, which is not a good thing when keeping track of things.

 

So if you only leave room for one digit try keeping only one digit....although that is just my opinion.

[Guest MrE]

I know this is marked as answered, but just to add some additional info.
The most common versioning I have seen would be "Semantic Versioning" I think - check it out

[Tigerbomb8]

I would do it like this  1.5.2

1st digit - major update

2nd digit - features added or chances made

3rd digit - bug fixes