Home > Development > Version Numbering

Version Numbering

I like this:

major: Really a marketing decision. Are you ready to call the version 1.0? Does the company consider this a major version for which customers might have to pay more, or is it an update of the current major version which may be free? Less of an R&D decision and more a product decision.

minor: Starts from 0 whenever major is incremented. +1 for every version that goes public.

release: Every time you hit a development milestone and release the product, even internally (e.g. to QA), increment this. This is especially important for communication between teams in the organization. Needless to say, never release the same ‘release’ twice (even internally). Reset to 0 upon minor++ or major++.

build: Can be a SVN/Git version, I find that works best.

For larger projects with many components Semantic Versioning makes sense, though it less end-user friendly.

Categories: Development Tags: , , , , ,
  1. No comments yet.
  1. No trackbacks yet.