Forum Moderators: coopster
As far as I can remember off the top of my head the numbers work like so
x.y.z
x == major version, all encompassing code changes, new features, bug fixes and minor changes rolled in for fun
y == minor version, some what extended with bug fixes rolled in for fun
z == bug fixes
essentially the first stable release would be 1.0.0
Well CVS is a method of version management. Personally I hate it
Care to elaborate? Is there a system that you like better or do you not like versioning systems?
I love being able to quickly see what's different, what's new, add comments and, above all, go back in time to a version that definitely worked.
I can also use it to figure out what has changed since the last synchronization of a live site and a local site.
I started using it for a couple of projects that had too many people involved to manage them any other way. Then I started using it even for things that I'm doing alone.
By the way, by default CVS will start your versioning out with
version 1.1.1.1 upon importing your code.
Your successive updates will go 1.1, 1.2, 1.3, 1.4 (two digits only).
Tom
I like it, but the only other thing I've tried (and still use in many cases) is to frequently create zipped archives and use some file/document comparison utility. It's okay, but I miss the ability to comment each version.
Tom