...
Source 5.0 also includes a range of upgrades and enhancements, as described below.
Date Range changes
Could this be under minor?
...
We have changed the version number system to help users understand when they need a new version of Source to open projects. The previous database version was a letter that wasn't in the version number.
The previous system was:
Order | Name | |
|---|---|---|
| 1 | Major Version number | |
| 2 | Prod/Beta identifier | All Prod numbers are even. All Beta identifiers are +1 the most recent Prod identifier |
| 3 | Regular Functionality Release | Incremented when a new Beta is released every 1 to 2 months. Rarely updated for Prod releases. |
| Not included in version number | Database Upgrade letter | Needed when changes are made that require DB upgrades between official releases. This is used to identify what the current database structure of the project will be. Resets to 'a' when the 'Regular Functionality Release' changes. |
| 4 | Build number | Essentially a unique identifier for Source builds |
New system:
Order | Name | |
|---|---|---|
| 1 | Major Version number | |
| 2 | Prod/Beta identifier/Regular Functionality Release | Reset when the Major Version number increments. Increments with every official Prod and Beta release. We may increase by more than +1 for production releases. |
| 3 | Database Upgrade Number | Needed when changes are made that require DB upgrades between official releases. This is used to identify what the current structure of the database's project will be. |
| 4 | Build number | Essentially a unique identifier for Source builds |
For example, under the previous system the last beta release would have been 4.12.4beta, but under the new system it was 4.13.1beta
...