Page Operations
Browse Space
Version Convention
Versioning of Velo releases follows an X.Y.Z convention where:
- X = The major release number - An increment of this number generally indicates a significant change to the code base. The increment may be completely incompatible with prior versions.
- Y = The minor release number - An increment of this number usually indicates a significant change to functionality or architecture but with a moderate to high level of backward compatibility with previous versions.
- Z = The maintenance release number - An increment of this number usually indicates bug fixing within the X.Y release and possibly small enhancements and limited new features. These versions are expected to be fully backwardly compatible with previous increments.
Structure
A new full release is denoted by a version number like X.Y (eg, 1.0). Each full release will be copied into it's own SCM tree where it can be maintained independantly of the development tree. Maintenance releases (eg, 1.0.1) will be release on an as-needed basis but approximately every two weeks during the initial period after the full release. This is aimed at improving the quality of stable releases that have been deployed by users and administrators and yield a better return on investment. You no longer have to wait for the next full release for a bug to be fixed.
Full releases will be subject to formal Alpha and Beta test periods. The lengths of these periods will be at the discretion of the Development Team but the Beta period should not be less than three (3) calendar weeks to allow for adequate compatibility testing by 3rd party developers.
Maintenance releases will be subject to in-house quality control only and will be made available for immediate use.
Closed
Resolved