This section contains the current release schedule and describes the rollout policy for Primo releases.
|Quarterly Release||MT Sandbox||TC||MT Production||Local|
|February 2017||January 22, 2017||January 29, 2017||February 5, 2017||February 12, 2017|
|May 2017||April 30, 2017||May 7, 2017||May 14, 2017||May 21, 2017|
|August 2017||July 23, 2017||July 30, 2017||August 6, 2017||August 13, 2017|
|November 2017||November 5, 2017||November 12, 2017||November 19, 2017||November 26, 2017|
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.
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