Ok, how about the following release version scheme?
Major.Minor.Point
-Point Release: No API changes, bug fixes, internal implementation
refactoring only.
-Minor Release: Expanded API for existing packages, new utility
packages,
no breaking of API backward compatibility.
Bug fixes, reimplementation or refactoring of existing
API functionality.
-Major Release: New Features, Packages & API, where those API
Changes could
potentially break backward compatibility and require
recompilation for existing applications.
I'm not suggesting we break backward compatibility, just that if we do,
it'll definitely be a major point release.
Cheers,
Peter.
