Release Types

## Major Release ### Description Major releases represents a pre-planned release available to all customers at the time of release. Major releases deliver iterative enhancements and new features to customers three times a year during seasonal releases: Spring, Summer, and Winter. Unlike Minor and Hotfix releases, Major releases are mandatory upgrades to your environment to keep your system upgraded with newest capability, enhancements and bug fixes. ### Release Dates Major releases usually coincide several weeks after the general availability of a Salesforce seasonal release. The date of availability for major releases is typically announced with 30 day notice. Generally speaking the Spring release is scheduled for March/April, the Summer release July/August, and the Winter release is November/December. The date of availability for a major release 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 Kaptio Customer Support Analyst will reach out via our helpdesk to your Kaptio System Administrator to announce the date of general availability for a Major release. Kaptio offers time slots for sandbox upgrades, and a time slot for production upgrade. General rule of thumb is to allow 2-weeks between the sandbox upgrades and the production upgrade. Release notes are made available before sandbox upgrades occur. This gives your team time to review new features, 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. ### General Considerations Major releases are required for all customers. To ensure your customization and integrations remain operational, please review the special considerations instructions for each release item. Kaptio recommends thorough testing of Major Releases within your sandbox environment prior to production upgrade. *** ## Minor Release ### Description Minor releases represents a small release containing a subset of features and improvements that are made generally available in a Major release. Minor releases are not made available to all customers. Unlike Major releases, Minor releases are optional upgrades to your environment and only offered to selected customers. Minor releases are often used to introduce improvements or new features that tactically help with new customer go-lives and to assist with adoption and business change management. ### Release Dates The date of availability for a Minor releases is announced with 14 day notice. Minor releases are not pre-planned, so there is no specific scheduled defined for Minor releases. Please note: The date of availability for a minor release 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 Kaptio Customer Support Analyst will reach out via our helpdesk to your Kaptio System Administrator to announce the date of general availability for a minor release. Kaptio offers time slots for sandbox upgrades, and a time slot for production upgrade. General rule of thumb is to allow 1-week between the sandbox upgrades and the production upgrade. Release notes are made available before sandbox upgrades occur. This gives your team time to review new features, 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. ### General Considerations Minor releases are only for selected customers. To ensure your customization and integrations remain operational, please review the special considerations instructions for each release item. *** ## 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.