Release Management Policy

Release Management Policy #

Last Updated: September 04, 2025

See What’s Changed

This Schedule outlines the Release Management Process for the HaaS Software.

1. Definitions and Interpretations #

a. The meaning of any general language is not restricted by any accompanying example, and the words ‘includes’, ‘including’, ‘such as’ or ‘for example’ (or similar phrases) do not limit what else might be included;

b. This Schedule is not to be interpreted against the interests of a party merely because that party proposed this Schedule or some provision in it or because that party relies on a provision of this Schedule to protect itself;

c. The following definitions apply:

  • Guides: refers to the Guides website at https://guides.biza.io.
  • Series: means a major release of the HaaS Software that may contain breaking changes. See here for more information.
  • Update: means a release within a HaaS Software Series.
  • Red: refers to Production spaces/environments.
  • Yellow: refers to Non-Production spaces/environments.

2. Release Process #

a. Biza will test New Series and Updates in accordance with its quality assurance processes;

b. Biza will notify Clients of a new Series or Update via a ticket and publish corresponding Release Notes on Guides. The ticket will include the proposed upgrade windows for both the Yellow and Red spaces.

c. Series and Updates will be automatically deployed in the the Yellow and Red spaces as per the notification unless the Client opts out or requests an alternative time within 14 days of notification.

Biza will use reasonable endeavours to minimise any downtime of the Software when deploying a new Series or Update. Biza may, at its sole discretion, deploy Security Updates without notice.