Versioning?

[sobrique]

Just had a conversation with a workmate.
It went something like this:

Him: "There's a new version of VCC out." (vmware virtual center).
Me: "Which version?"
Him: "1.2"
Me: "Wasn't that out a few months ago."
Him: (sardonically) "Yes. They've re-released it. But they've updated the build number".
Me: *swearing about a lack of understanding of version numbers*

Comments

[warmage.livejournal.com]

Rule #1: Never jump on anything with a version number ending in ".0".
Rule #2: Never jump on an update without first reviewing the changelist.
Rule #3: If the changelist doesn't exist or doesn't touch solve a problem you're currently having - Don't bleedin' use it!

...right?

[sobrique.livejournal.com]

Rule 0. If it's an 'updated' version, and you're using version numbers, then change the feckin' version number too. It's no good me telling you 'we're running 1.2' if you're just going to come back and ask 'which version of 1.2'.

grrr...

Axiom: "All first releases of major updates will be dangerously flawed. Use at your own peril".

(1.0, 2.0. etc. get as far as dev machines, and we leave them running. _guaranteed_ someone will have found a 'show stopper' within 3 months)

[warmage.livejournal.com]

'struth :)