What do the numbers in a version typically represent (i.e. v1.9.0.1)?

versions
BeachRunnerFred picture BeachRunnerFred · Sep 15, 2008 · Viewed 88.2k times · Source

Maybe this is a silly question, but I've always assumed each number delineated by a period represented a single component of the software. If that's true, do they ever represent something different? I'd like to start assigning versions to the different builds of my software, but I'm not really sure how it should be structured. My software has five distinct components.

Answer

Dillie-O picture Dillie-O · Sep 15, 2008

In version 1.9.0.1:

  • 1: Major revision (new UI, lots of new features, conceptual change, etc.)

  • 9: Minor revision (maybe a change to a search box, 1 feature added, collection of bug fixes)

  • 0: Bug fix release

  • 1: Build number (if used)—that's why you see the .NET framework using something like 2.0.4.2709

You won't find a lot of apps going down to four levels, 3 is usually sufficient.

Related questions

SVN (Subversion) Problem "File is scheduled for addition, but is missing" - Using Versions

I'm using Versions for SVN. I attempt to commit and get this message: Commit failed (details follow): '/Users/mike/Sites/mysite.com/astss-cvsdude/Trunk/cart/flashfile.swf' is scheduled for addition, but is missing I suppose this is because …

Read More
resolving simple svn conflicts

I'm a bit of newcomer to using svn on a mac. I'm using Versions. I've been getting reports that I've been overwriting other devs work, so I'm hoping someone here can make sure I'm doing things properly. I committed my …

Read More
How best to use File Version and Assembly Version?

In .NET there are two version numbers available when building a project, File Version and Assembly Version. How are you using these numbers? Keeping them the same? Auto-incrementing one, but manually changing the other? Also what about the AssemblyInformationalVersion attribute? …

Read More