Skip to main content
Ex Libris Knowledge Center

Primo Release Schedule and Rollout Policy

This section contains the current release schedule and describes the rollout policy for Primo releases. For Primo VE, see the Primo VE Release Schedule.

Release Schedule

Quarterly Release Schedule - 2024
Quarterly Release MT Sandbox Total Care (TC) MT Production Local
November 2023 October 22, 2023 October 29, 2023 November 5, 2023 November 19, 2023
February 2024 January 21, 2024 January 28, 2024 February 4, 2024 February 18, 2024
May 2024 April 21, 2024 April 28, 2024 May 5, 2024 May 19, 2024
August 2024 July 21, 2024 July 28, 2024 August 4, 2024 August 18, 2024
November 2024 October 20, 2024 October 27, 2024 November 3, 2024 November 17, 2024


  • 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

Streamlining the release process will allow Institutions to –
  • 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

The following diagram presents the Primo version release rollout workflow:
Rollout Workflow Diagram
  • Was this article helpful?