Each monthly release contains new features or feature enhancements, as well as maintenance items. Additional maintenance releases occur on Tuesdays and Thursdays.
These dates are approximate. Your system may be updated a couple days before or after.
| Release Number | Release to Test Servers* | Release to Production Servers* |
|---|---|---|
| v3900.106.0 | 12 November 2024 | 5 December 2025 |
| v3900.108.0 | 10 December 2024 | 9 January 2025 |
| v3900.110.0 | 14 January 2025 | 6 February 2025 |
| v3900.112.0 | 11 February 2025 | 6 March 2025 |
| v3900.114.0 | 11 March 2025 | 3 April 2025 |
| v3900.116.0 | 8 April 2025 | 1 May 2025 |
| v3900.118.0 | 6 May 2025 | 5 June 2025 |
| v3900.120.0 | 10 June 2025 | 3 July 2025 |
| v3900.122.0 | 8 July 2025 | 7 August 2025 |
| v3900.125.0 | 12 August 2025 | 4 September 2025 |
| v3900.127.0 | 9 September 2025 | 2 October 2025 |
| v3900.129.0 | 7 October 2025 | 6 November 2025 |
| v3900.131.0 | 11 November 2025 | 4 December 2025 |
| v3900.133.0 | 9 December 2025 | 8 January 2026 |
| v3900.136.0 | 13 January 2026 | 5 February 2026 |
| v3900.138.0 | 10 February 2026 | 5 March 2026 |
What does the release version number mean?
Blackboard uses a combined versioning schema for all deployments: 3900.x.-rel.abcdefg. Each digit has a specific meaning.
- x – Represents the “minor” version for a given release. E.g. 3900.1 = the first continuous delivery release after the 3900 release.
-rel.abcdefg – Represents the specific build number for a release. This build number is only relevant for technical troubleshooting and internal Blackboard development systems and can generally be ignored by most customers. Blackboard Support may request this build number for validation when clients submit support cases.
The build number may differ between a release's stages (Test/Staging and Production). If you notice that a release's build number in your Test or Staging environment doesn't match the release's build number in your Production environment, this is normal and expected.
