Hi All,
Since I'm not convinced that everyone is familiar with VWG versioning procedure and version numbering system, I would like to share some important information with you regarding our versions, revisions, releases and roadmap, and hopefully make them clearer.
- Version:
A Version is a new build with newly developed capabilities.
The Version number has 4 digits; the first pair represents the version number and the second pair represents the build number:
[Major].[Minor] (build [Build-Major].[Build-Minor]) e.g., “1.0 (build 5.83)”.
- Release:
At some point, after a certain predetermined content is developed, a version is called a Release Version which will be noted by “R” right after the version number:
[Major].[Minor]R (build [Build-Major].[Build-Minor]) e.g., “1.0R (build 6.0)”.
- Revision (Stabilization Build):
After releasing a version, any stabilization fixes are released as a revision of that version.
A Revision is indicated by another number added after the build number, separated by a period:
[Major].[Minor] (build [Build-Major].[Build-Minor].[Revision]) e.g., “1.0 (build 5.83.3)”.
At any given point in time, there are 3 relevant versions:
- The Current Stable Version - an older version with an advanced stabilization build, which is considered the most stable but least recent, having been stabilized by the community and reviewed by the core VWG development team.
- The Current Un-Stable Version – a release more recent but less stable than the Current Stable Version, since it was not sufficiently reviewed by the community and the core VWG development team to be considered stable.
- The Next Version – a version, which has not been released yet. This is the version that the core VWG team is working on currently to create the next Un-Stable version at a predetermined date.
The Current Stable Version and Current Un-Stable Version can be downloaded from the developers VWG download page on the web site.
The VWG issue tracker holds the latest information regarding:
- Versions Road-Map which is a list of issues (bugs, features, enhancements etc.) to be handled on each planned version. Each version, for which the VWG core team has a set a target date, will have a Due Date shown.
- Versions Change-Log, which is a list of issues (bugs, features, enhancements etc.), fixed on a specified released version.
- Unscheduled issues that are reported but not yet assigned to a version. The VWG code team reviews this list periodically to validate and schedule issues.