Patch Release

Description

Patch releases represents a release dedicated for fixes to critical bugs. A patch is usually meant to fix an issue that got introduced in a minor or major release. As Kaptio releases are introduced using a staggered rollout approach, patch releases usually don’t affect all customers.

Release Dates

The date of availability for a patch releases is announced with 3 day notice.

The date of availability for a patch releases is not the same as the actual upgrade date to your environment. The upgrade date is a mutual decision by Kaptio & the customer (see Release Process).

Release Process

A patch release comes about in one of two ways:

  • During routine regression testing, Kaptio realise the issue and the affected releases. Customer Support team notifies affected customers and a mutual action plan is defined.

  • Customer might identify the issue, either in a production environment or in a pre-release sandbox state. The issue would get reported via Customer Support and a mutual action plan is defined.

Release notes are made available before sandbox upgrades occur. This gives your team time to review the changes and test the new environment.

During the release process, a support ticket will be In used to track discussions & troubleshooting for the release process. For cases where more time is needed between sandbox or production upgrade, the planned production upgrade slot can be changed.

The fixes introduced via the patch are made available as part of the next Major or Minor release for future customers.

General Considerations

Patches releases usually only affect selected customers. The Customer Support team notifies affected parties and builds a mutual action plan.

As with other release types, to ensure your customization and integrations remain operational, please review the special considerations instructions for each release item in the patch release.