What does the release version number mean?

Blackboard Learn uses a combined versioning schema for all deployments of the format: X.Y.Z-rel.abcdefg. Each of the digits and information in the versioning schema has a specific meaning.

X – the first number in the schema represents the “major” Q2 or Q4 version for a given release. E.g. 3100 = Q4 2016, 3200 = Q2 2017, etc.

Y – the second number in the schema represents the “minor” version for a given release and is relevant only to SaaS Continuous Delivery customers. E.g. 3100.1 = the first Continuous Delivery release after the 3100 / Q4 2016 release.

Z – the third number in the schema represents the “point” version for a given release and aligns with Cumulative Updates for major Q2 or Q4 releases available to Self-Hosted, Managed Hosting, and SaaS Flexible Deployment customers. E.g. 3100.0.1 = Cumulative Update 1 for Q4 2016 release.

-rel.abcdefg – the last piece of information in the schema 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.

Continuous Delivery release schedule

Each release contains new features or feature enhancements, as well as maintenance items.

Release notes are published on or about the same day a release reaches Test servers.

All releases in continuous delivery are cumulative. For example, v3000.5.0 includes all content from v3000.4.0 and previous releases. Where a cell is marked with a dash ("-"), this release was not applied to the noted environment and changes will be rolled into the next release.

*These dates are approximate. Your system may be updated a couple days before or after this date.

**Help documentation refers to help topics for students, instructors, and administrators. Release notes are published on or about the same day a release reaches Test servers.

***This release was formerly numbered 3800.0.0. We bumped the version number to 3700.11.0 to reflect alignment with 9.1 and SaaS FDO releases with compatible Java versions. All subsequent release numbers have been updated to reflect the new number series. Release dates remain unchanged.

****This release was formerly numbered 3600.2.0. We bumped the version number to 3700.0.0 to reflect alignment with 9.1 and SaaS FDO releases with compatible Java versions. All subsequent release numbers have been updated to reflect the new number series. Release dates remain unchanged.

Flexible Deployment Option release schedule

Starting with the 3200.0.0 release (FDO Q2 2017), Flexible Deployment releases follow a different schedule than Continuous Delivery releases. Instead of a set deployment date for the release to Production instances, Blackboard provides multiple update windows for SaaS FDO customers to choose from. To select an update window, please contact Customer Support. If a customer doesn’t request a specific update window, the system receives the release on the last available date and time.

Starting July 2020, Blackboard will no longer support the Flexible Deployment Option for SaaS environments. Blackboard Learn SaaS will only be delivered in a continuous delivery cadence at this date. For more information on how and when this change affects you, visit Behind the Blackboard.

Release Number

Release to Test Servers*

Date Options for Release to Production Servers

v.3700.0.3 / Q2 2019 CU 3

15 August 2019

28 August 2019

v.3700.0.2 / Q2 2019 CU 2

3 July 2019

17 July 2019

v3700.0.1 / Q2 2019 CU 1

5 June 2019

20 June 2019

v3700.0.0 / Q2 2019

1 May 2019

16 May 20191

30 May 20191

v3500.0.5 / Q4 2018 CU5

11 April 2019

25 April 2019

v3500.0.4 / Q4 2018 CU4

25 February 2019

14 March 2019

v3500.0.3 / Q4 2018 CU3

6 February 2019

21 February 2019

v3500.0.2 / Q4 2018 CU2

10 January 2019

24 January 2019

v3500.0.1 / Q4 2018 CU1

27 November 2018

13 December 2018

18 December 2018

v3500.0.0 / Q4 2018

18 October 2018

15 November 2018

*These dates are approximate. Your system may be updated a couple days before or after this date.

1 We've shifted the Production release dates for Q2 2019 (3700.0.0) in response to client feedback. Clients who wish to receive Q2 2019 (3700.0.0) on either May 16th or May 30th can file the request via a support case on Behind the Blackboard. All FDO clients will receive Cumulative Update 1 to Production environments on June 20th.