Release Management Process

Release Management Process #

Last Updated: September 04, 2023

See What’s Changed

This Schedule outlines the Release Management Process for the Services.

  1. Definitions and Interpretations

    1. 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;

    2. 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;

    3. The following definitions apply:

      Guides
      refers to the Guides website at https://guides.biza.io .
      Breaking Change Release
      means a release of a new version of the Services, which contains a modification to an existing functionality that cannot function without changes implemented by the Client (for example a Client delivered API containing new required fields).
      New Release
      means new and updated versions of the Services including Breaking Change Release, Security Release and General Release.
      Security Release
      means a release of a new version of the Services, which is not a Breaking Change Release, but rectifies a security vulnerability
      General Release
      means a release of a new version of the Services, which is not a Breaking Change Release, but contains new functionality or bug fixes

  2. Release Process

    1. Biza will publish changelogs for New Releases on Guides;
    2. Biza will test New Releases according to its quality assurance processes;
    3. Biza will release New Releases into its production environment as soon as possible;
    4. The Client will decide when to start using features introduced as part of a New Releases;
    5. Biza will release New Releases no later than the applicable date specified in any legal obligations outlined within the appropriate Statements of Work;
    6. Biza will use reasonable endeavours to minimise any downtime of the Services when releasing New Releases;
    7. Biza will coordinate a change into the designated testing environment to allow for Client testing and then promote these changes, in consultation with the Client into Production;
    8. Biza will provide updated specifications at least 30 Business Days prior to any Breaking Change Release being made;

  3. Release Timelines

    1. Biza may, at its absolute discretion, deploy Security Releases without notice;
    2. Biza will provide the Client with at least 10 Business Days’ noCce of any General Release;
    3. Biza will provide the Client with at least 20 Business Days’ noCce of any Breaking Change Release