Release Process
This page outlines how we release, support, and retire Biza Open Gateway Software.
Biza has designed the release and support process to make Open Gateway (OG) releases straightforward, ensure compliance, and provide a predictable experience. Here's how it works:
Release Definitionsβ
- Series: This refers to a major OG Software release. A new Series is available roughly every 180 days and marks a new baseline for features and support.
- Updates: This refers to releases within a Series.
Updates apply automatically to your environments. They do not include breaking changes and therefore cannot be opted out of.
A new Series may contain breaking changes that require work on the customer-side. We will provide advance notice of any such changes, including details of deprecated functionality that will be retired in the next Series. If necessary, you can choose an alternative deployment timeframe for a new Series to allow more time to prepare for and implement any required changes.
Metadata Endpoint Version Supportβ
For each Series or Update, we will highlight the new metadata endpoint versions, which you can use to understand the version of the API endpoints you require to comply with any Future Dated Obligations.
Release Types Summary and Lifecycle Managementβ

OG Release Process
The table below summarises the OG 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 Type | Frequency | Available for Deployment | EoL | Impact | Future Dated Obligations |
|---|---|---|---|---|---|
| Series | ~ every 180 days | March and September | T + 360 days | Usually contains breaking changes (deprecation announcements and retirements). These will be contained in a schedule outlined in the Series release. βͺ Remove deprecated CDR API versions | May enable new FDO support as per the DSB and OG software schedule. |
| Update | As required (usually every 2-4 weeks) | Upon notification | All Updates to a Series reach EoL on the same date as the Series. | Backwards compatible within the same Series. βͺ Features, bug fixes. βͺ Perfomance and stability improvemments βͺ Security and vulnerability fixes. | May enable new FDO support as per the DSB and OG software schedule. |
Seriesβ
A Series defines a new baseline for features and support.
Series Characteristicsβ
- A Series may outline scheduled breaking changes and the timeframe for their retirement.
- Breaking changes will first be announced as deprecated before being retired in the following Series release.
- This release may not be backward compatible and thus requires action to avoid interruptions to services.
- May add support for Future Dated Obligations (FDOs).
- Each Series has a defined End-of-Life (EOL) 360 End-of-Life (EoL) period. After this date, no further Updates will be released and support will cease.
- Two Series will run concurrently and be fully supported.
Updateβ
An Update is a non-breaking release within an active Series.
Update Characteristicsβ
- Applied automatically to all active environments (Yellow and Red).
- Adds support for new CDR API versions.
- Enables new Future Dated Obligations (FDOs).
- Backwards compatible within the same Series.
- Will be applied concurrently across multiple active Series until EoL.
- May include
- Bug fixes.
- Performance and stability improvements.
- Security and vulnerability fixes.
- Minor features and enhancements.
Release Managementβ
Hereβs how we manage each new Series or Update to the OG Software, and what you can expect.
How releases are sharedβ
- We will inform you when a new Series or Update is available.
- On announcement of a Series release, a schedule of breaking changes and their retirement timeframe will also be provided.
- Supporting Release Notes will be published 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.
Release coordinationβ
- We will notify you when a new release is ready.
- Updates will be automatically applied across all your environments following notification.
- For Series releases, 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 release to your Yellow environment.
- You will have a window to test any changes required to support a new Series in your Yellow environment, after which we will deploy the series release to your Red environment. This will require you to agree to a deployment window by approving a change request.
What you need to doβ
- Keep your contact detail up-to-date, including phone numbers and email addresses.
- Monitor release communications and plan support for deprecated changes in advance of their retirement in the following Series.
- Review the release notes with the attached reference test results.
- Let us know if you prefer to opt out a Series release within 14 days of notification.
- Requests for changes to the Red installation date must be raised 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.
- Conduct Production Verification Testing (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 OG 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.
Question and Supportβ
If you have any questions about this release plan or need assistance with upgrading, please contact our support team.