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 Alma Release Schedule.

Release Schedule

Quarterly Release Schedule - 2019
Quarterly Release MT Sandbox TC MT Production Local
February 2019 January 20, 2019 January 27, 2019 February 3, 2019 February 17, 2019
May 2019 April 28, 2019 May 5, 2019 May 12, 2019 May 26, 2019
August 2019 July 21, 2019 July 28, 2019 August 4, 2019 August 18, 2019
November 2019 November 10, 2019 November 17, 2019 November 24, 2019 December 8, 2019
Quarterly Release Schedule - 2020
Quarterly Release MT Sandbox TC MT Production Local
February 2020 January 19, 2020 January 26, 2020 February 2, 2020 February 16, 2020
May 2020 April 26, 2020 May 3, 2020 May 10, 2020 May 24, 2020
August 2020 July 19, 2020 July 26, 2020 August 2, 2020 August 16, 2020
November 2020 November 08, 2020 November 15, 2020 November 22, 2020 December 6, 2020

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?