How do you version your projects? [closed]

Answer 1

Major.Minor.BugFix.SVNRevision

e.g: 3.5.2.31578

• The SVN Revision gives you the very exact peace of code sent to the customer. You are absolutely sure if that bugfix was there or not.
• It also helps finding the proper PDB in the event you have an application error. Just match the SVN Revisions on your build server, copy the PDB to EXE location, open the debugger and you got the crash stack trace.

Answer 2

I use major.minor.point.revision, where point is a bugfix-only release and revision is the repository revision. It's easy and works well.

Answer 3

I just do Major.minor. Since I'm a single developer (with occasional help) working on a web app most people couldn't care less about the minor fixes that I make. So I just iterate up the minor versions as I put in new features and major version numbers when I make some whopper of a change/upgrade. Otherwise, I just ignore the small fixes as far as version numbers go (though I do have Subversion revision numbers if I need to refer back for myself).

Answer 4

We generally do major.minor[.maintenance[.build]] where I work, but it seems to vary a little per project.

Major/minor the same as you mentioned. maintenance would be incremented for small (bug) fixes and build for each time the build server runs.

Answer 5

I used to like the Nantucket way of versioning their Clipper compiler in the 80's:

Clipper Winter 1984
Clipper Summer 1985
Clipper Winter 1985
Clipper Autumn 1986
Clipper Summer 1987

Oh and overlays....

[gets teary eyed]

Answer 6

I just have a number. First release is 001. Second release's third beta is 002b3, and so on. This is just for personal stuff mind, I don't actually have anything 'released' at the moment, so this is all theory.