Version numbering basics? [closed]

Question

Suppose I have a web application with some basic functions. I want to market it. So I would like to assign a version number - something like 0.0.1. What I want to know is are there any constraints that should apply to that numbering system?

Hope you understood my question, thanks in advance.

Answer 1

When developing software libraries, I recommend using the version number to communicate the level of source and binary compatibility between two releases.

Since you're developing a web application, a two part version number is probably sufficient. The first part is for new functionality and the second is for fixes.

Answer 2

You can use any form of version numbering you desire.

I just recommend using something that makes sense. The Major.Minor.Revision numbering is popular, but any numbering scheme you wish is "valid".

Answer 3

I seem to remember that in the old days (I am talking Commodore here) we used a syntax like release.version.revision which could be appended with either fix and/or build, where fix would usually be a letter stuck directly to the revision. So a full number would read something like:

2.1.44a.786

But like most have already said, it doesn't really matter, there is no true standard for this. Just use whatever is most convenient for you.

Answer 4

After reading a lot of articles/QAs/FAQs/books I become to think that [MAJOR].[MINOR].[REV] is most useful versioning schema to describe compatibility between project version (versioning schema for developer, does not for marketing).

MAJOR changes is backward incompatible and require changing project name, path to files, GUIDs, etc.

MINOR changes is backward compatible. Mark introduction of new features.

REV for security/bug fixes. Backward and forward compatible.

This versioning schema inspired by libtool versioning semantics and by articles:

http://www106.pair.com/rhp/parallel.html

NOTE: I also recommend provide build/date/custom/quality as additional info (build number, build date, customer name, release quality):

Hello app v2.6.34 for National bank, 2011-05-03, beta, build 23545

But this info is not versioning info!!

Answer 5

You can use whatever numbers you want in your versioning - who's going to constrain you?

If you want your first version to be 0.0.0.0.0.0.0.1, that's fine, albeit a little silly. If you want your first version to be 106.3, you can do that too, but that's a little more ridiculous.

Check out the Wikipedia article on Software Versioning for some tried-and-true ideas of realistic version numbering schemes.

Answer 6

I've always used (rewrite).(feature added).(bug fix).

But set your own rules and make them public so your users understand them.