10

Are there any software versioning standards? Or i can change version of my product, when i have made some changes to it?

Is there any percentage in changes, by which i can say, what version this product will have?

Yurish
  • 1,307
  • 1
  • 25
  • 44
  • For end-user software you can practically run wild and let PR handle the version numbers. For libraries you should go a more engineering-like route ;-) – Joachim Sauer Mar 12 '10 at 10:25
  • See also: - http://stackoverflow.com/questions/65718/what-do-the-numbers-in-a-version-typically-represent-i-e-v1-9-0-1 - http://stackoverflow.com/questions/615227/how-to-do-version-numbers - http://stackoverflow.com/questions/1889615/version-numbering-basics – Konrad Garus Mar 12 '10 at 10:16
  • Especially http://stackoverflow.com/questions/615227/how-to-do-version-numbers – T.J. Crowder Mar 12 '10 at 10:18

2 Answers2

12

Some people have proposed software version number conventions. Here are two:

Greg Hewgill
  • 951,095
  • 183
  • 1,149
  • 1,285
4

No rules. You decide.

There seems to be a common agreement:

  • You increment the version number when you make significant changes or the amount of service packs and updates makes the application noticeably advanced over the original version.

  • The smaller a change is, the smaller the increment in subversion numbers. Bug fix -> behavior change -> new feature -> service pack for lots of features -> some big change or a new module.