Primo Release Schedule and Rollout Policy
Release Schedule
| Quarterly Release | MT Sandbox | Total Care (TC) | MT Production | Local |
|---|---|---|---|---|
| November 2024 | October 20, 2024 | October 27, 2024 | November 3, 2024 | November 17, 2024 |
| February 2025 | January 19, 2025 | January 26, 2025 | February 2, 2025 | February 16, 2025 |
| May 2025 | April 20, 2025 | April 27, 2025 | May 4, 2025 | May 18, 2025 |
| August 2025 | Given the minimal content scheduled for this release, we've streamlined this year's release schedule by combining it with our November release, eliminating unnecessary testing cycles with little added value for institutions. | |||
| November 2025 | October 19, 2025 | October 26, 2025 | November 2, 2025 | November 16, 2025 |
Key:
-
MT - Cloud environment consisting of multiple tenants who perform their own configuration at the institution level in the Primo Back Office.
-
TC - Cloud customers who have limited access to the Primo Back Office.
-
Local - Customers who own and maintain their own Primo servers.
Release Timeline and Rollout
Updates to Primo are delivered every three months. These updates include security issues, new features, feedback on design issues, escalations related to specific functionality, and other issues.
Ex Libris upgrades cloud environments as soon as a new release of Primo is available, following an extensive QA process. We make certain that our hosted customers are the first to benefit from the latest enhancements and bug fixes.
By establishing the structured process, upgrades are more frequent and the gap between the current version and the new version is small.
The rollout of each new version is gradual and begins with institutions that are using Primo in the Ex Libris cloud environment. Prior to the upgrades, a message notifying cloud customers of the date of the upgrade will be sent out by the cloud team.
The upgrade process will consist of two steps: first, the new release is installed on the sandbox environment where applicable. We trust that you will try out the new version during this time. Two weeks later, the new release is installed on the production environment. Consortia environments will have a four weeks test period.
Five days in advance, Dedicated customers will receive a message containing the exact install dates for both sandbox and production, which will occur within five weeks of the MT sandbox installation date.
Key Benefits
-
Enjoy higher quality enhancements and fixes in a shorter timeframe
-
Ensure that customizations are most accurately preserved
-
Enjoy the predictability of service pack releases
Release Rollout Flow
