The version numbers that are applied to updates give information about the kinds of changes made in the updates.
This Tech Note describes what the version numbers mean.
So you have heard about continuous delivery and continuous deployment and you are eager to try, but your manager is afraid that you will lose traceability of the project.
Since the APR projects are libraries, it is very important to define a stable API for users of the libraries.The ‘5’ in ‘HDF5’ is part of the product name and will not change during the life of the project.The key components in HDF5 Library version numbers are the major version number, the minor version number, the release number, and an optional text string.However, we also need to move the libraries forward, technologically.To balance these two needs, a strict policy of versioning is required, which users can rely upon to understand the limitations, restrictions, and the changes that can occur from one release of APR to the next.Preprocessor macros used to determine the ATL or MFC library version are not predefined by the compiler.These macros are defined in the headers for the library, so they are undefined in preprocessor directives before the required header is included.Before a 1.0 release (version 0.x.y), the API We define "source compatible" to mean that an application will continue to build without error, and that the semantics will remain unchanged.Applications that write against a particular version will remain source-compatible against later versions, until the major number changes.The traditional Java community way of version handling with a three digit number, potentially followed by a build number or a qualifier, e.g. RELEASE, works well if you have long development cycles with the occasional bugfix release in between.The problem is that it does not scale when the frequency of releases increases by a magnitude or two.