๐ข Release Management Process
This page outlines how we release, support, and retire the Biza HaaS Software.
Biza has re-designed the release and support process to make HaaS releases straightforward, ensure compliance, and provide you with a predictable experience, and greater control and flexibility around when you deploy releases. Hereโs how it works:
Release Definitionsโ
To avoid confusion and keep things simple, weโve changed the way we refer to releases:
- Series: This refers to a major HaaS Software release. A new Series is available roughly every 180 days and marks a new baseline for features and support.
- Updates: This refers to the releases within a Series.
Simple Support: Only Two Series at a Timeโ
At any given time, we support only the two most recent Series of the HaaS Software. When a new Series is launched (about every 180 days), the previous one will continue to receive important bug fixesโbut no breaking changesโfor another 180 days. After this 12 month period, it reaches End-of-Life (EoL). You donโt need to upgrade immediately when a new Series is available, but you will need to move to a supported Series within the 12-month window.
What this means for youโ
You will always be supported on the current and previous Series, with clear timelines for upgrades, so you can plan ahead.
Easy Updates Within Each Seriesโ
To streamline the experience and help you stay current with minimal effort, Updates will be applied by default. This means the latest improvements and fixes will be installed in your Yellow space for testing prior to moving to Red, unless you choose to opt out. In cases where an Update includes a critical security or stability fix, moving to the latest version may be required to ensure your environment remains secure. These requirements will always be clearly outlined in the release notes.
What this means for youโ
You can always move directly from your current Update to the latest one in your Series, making upgrades quick and simple.
Metadata Endpoint Version Supportโ
For each Series or Update, we will highlight the supported metadata endpoint versions, which you can use to understand the version of the Biza Data Adapter API endpoints you require. Breaking changes or removal of metadata versions will only occur in Series releases.
What this means for youโ
This means you can safely upgrade without the risk of unexpected changes to your configuration or integration.
Release Types Summary and Lifecycle Managementโ
The table below summarises the HaaS release types and lifecycle for each type.
Please plan your upgrade to the next supported Series well ahead of your current Series' EoL date. Be sure to factor in the impact of the changes, time for code updates and any coordination required with third-parties.
| Release Types | Frequency | Available for deployment | EoL | Impact | Future Dated Obligations |
|---|---|---|---|---|---|
| Series | ~ every 180 days | March and September | T + 360 days | Usually contains breaking changes. โช Remove deprecated data adapter versions. โช Minimum data adapter versions for FDOs. | Will enable new FDO support as per the DSB and HaaS software schedule |
| Update | As required | Upon notification. We aim to give advanced notice, but in rare cases, we may force a Security Update without notice to protect your environment. | All Updates to a Series reach EoL on the same date as the Series. | Backwards compatible within the same series. โช Features, bug fixes โช Performance and stability improvements. โช Security and vulnerability fixes. | Where applicable, updates may include changes to support FDOs. This will be made clear in the Release Notes. |
Release Management
Hereโs how we manage each new Series or Update to the HaaS Software, and what you can expect.
How releases are sharedโ
- We will let you know when a new Series or Update is available.
- Supporting Release Notes will be provided to explain what is changing and any actions required, including;
- Applicable FDOs
- Bug fixes
- New features and enhancements
- Specification updates, where required
- Biza Test Suite (BTS) results specific to your industry.
Each new Series or Update for HaaS will now be put through our internal Quality Assurance (QA) process before itโs available to you. This includes testing against the Biza Test Suite (BTS), which will be run on a centrally managed model environment - a standardised test instance maintained by us to ensure consistency across releases.
Note that packaged Biza Test Suite results will no longer be available for specific HaaS spaces. Instead, the reference test results based on our model deployments will be published in the Release Notes. We recommend customers utilise the automated testing capability already available within Verification Testing Tool (VTT).
Release coordinationโ
- Weโll let you know via a ticket when a new release is ready, including the proposed installation windows for your Yellow and Red environments. As a general guideline, deployment to your Yellow environment is scheduled 14 days after notification, with deployment to your Red environment planned 14 days after the Yellow upgrade.
- You may choose to opt out or propose a new window within 14 days of notification. If we donโt hear from you, we will proceed with the proposed dates.
- If you need to change your installation date for Red, request this through a Production Change Request ticket. Please provide the proposed new date and time and wait until we have updated the time before approving the change ticket.
- Change tickets must be approved 5 business days before the change is scheduled.
- If you need to cancel or change the installation date after you have approved a change ticket, please ensure that the Designated Approver responds in the ticket with a comment to confirm the cancellation. Please provide the proposed date and time if the change needs to be rescheduled (note that the proposed date will need to be confirmed by Biza, and we will update the ticket).
What you need to doโ
- Keep your contact detail up-to-date, including phone numbers and email addresses.
- Monitor release communications and plan upgrades in advance.
- Review the release notes with the attached reference test results for your industry.
- Let us know if you prefer to opt out of installing a Series or Update within 14 days of notification.
- Requests for changes to the Red installation date must be through a Production Change ticket and include the proposed new date and time. Please wait until we have updated the time before approving the change ticket.
- Approve your change ticket at least 5 business days before the change is scheduled.
- Use the Verification Testing Tool (VTT) for Acceptance Testing (AT) prior to deployment to your Red space.
- Once your upgrade window has been confirmed, schedule an outage using our HaaS manager tool so that your ACCC availability metrics are not affected.
- Conduct PVT within your agreed change window and let us know if you find any issues.
- Ensure your systems and processes are compatible with the supported series.
Summaryโ
Our approach limits the number of supported HaaS Software Series, streamlines upgrades, and ensures complianceโmaking it easier for you to stay current, secure, and supported, with a clear and predictable path forward.
Questions and Supportโ
If you have any questions about this release plan or need assistance with upgrading, please contact our support team.