How are version numbers made?

Question

What decides what number will be used for a version number in a program?

Answer 1

Version numbers go like this:



A program starts off at say, 0.1 then 0.1.5 if it were a minor update, if it were significant, perhaps it'd be 0.2.



This happens until it reaches 1.0- meaning it's out of beta/testing phase and it's the first major release of the product.



1.0.5 would be likely if there were some bugs in the first major release, and there were fixes. 2.0 would be the next major update, and so forth.



Get what I'm saying?

Answer 2

It's actually a number system made up by the programmers. It's a way of denoting which build they are on (how many changes from the original program). Since it's a number system made by the programmer, it's different from program to program.



Usually, it starts off as 1.0. That denotes the first build. If they update it, it usually goes up to something like 1.1. When it gets to a point where they change large amounts of the code, it will jump up to 2.0 (because it wasn't just a small update, it was a large change). etc.

Answer 3

Theres no law as such, however as a rule of thumb



My App Version 1.2.34.4355



1

Would be the First final working version (the one you give to your customers)



.2

The Second Major revision (enogth to make a big difference but not a new version) (think major bug fix, i.e. security flaw)



.34

The 34th Minor revision (Minor bug fix) (think spelling correction in a dialog box)



.4355

The four thousanth three hundreth and fifty-fith re-compiling of the source code.