How to set milestones (i.e. versions)?

Hi,

I am just curious to understand if there is any specific process in setting milestones, such as version 1.01 or version 1.1 or version 2.0.

Is it just up to your own judgement or is there some sort of specific methodology for selecting these milestones points?

Here’s basically what I’ve settled on:

  • 1.x or 2.x is a major change: lots of feature and code changes; pretty much a rewrite of the application
  • 1.1 to 1.2 is a medium change: some additional features, some fixes, some code changes
  • 1.1.1 to 1.1.2 is a minor change: mainly just bug fixes
  • 1.1.1a1 to 1.1.1a2 is an alpha for internal use only
  • 1.1.1b1 to 1.1.1b2 is a public beta
  • 1.1.1b2 to 1.1.1 is a beta to a final release

There’s also build numbers that get thrown into the mix to help keep track of versions while in development. These are sometimes used in place of version numbers.

Very good system Force, I think that is reasonable and fairly adaptable by anyone seeking to have their own Version System. Although, the Alpha and Beta would be better suited for larger companies, or those who just like to get extremely technical.