We wanted to give you some clarifications on the terms we use at Configura when talking about updating CET. As performance remains our top priority, we aim to distribute releases every other week for as long as something adds value for our community. With that release cadence, you will experience different types of releases and it’s important you understand what they mean and how they impact you as a user.
As we execute this bi-weekly release cadence, we will monitor the value of the content contained within the releases to ensure you receive value and not disruption. If we don’t have any high-value fixes to release, we’ll wait for a later date. This allows our team at Configura to focus on quality in parallel to performance through thorough development and quality assurance practices.
Definitions of Major and Minor CET Releases
Major Release
Frequency: Twice per year; one in May and one in November
- Scheduled release; largest update to users and manufacturers
- Includes new features
- Always requires manufacturers to migrate
- Requires users to update CET
- Read more here
Minor Release
Frequency: Twice per year; one per Major Release – one in February and one in August
- Scheduled release; second largest update to users and manufacturers
- Includes new features
- Requires users to download updates
- Usually, it is not required for manufacturers to migrate their Extensions. Interface changes can be allowed in certain scenarios when its clearly communicated to affected parties what they need to migrate
Definitions of Patches, Hotfixes and First-Aids
Patches
Frequency: Four times per year; two per Major Release; one month after major and one month after minor
- Bug fixes that are not urgent for a Hotfix
- Requires users to download updates
- Does not require manufacturers to migrate their Extensions
- Typically, fixes issues that are reported by users through support, dev support, & our crash collecting software
Hotfix
Frequency: As needed
- Typically, unplanned
- Most urgent fixes that need to be done to ensure good performance and cannot wait until next planned patch
- Most often fixes something that just got released in the prior release
- Made to have a minimal impact
First-Aid
Frequency: As needed
Can be used when a Hotfix is for some reason unavailable to a small subset of our users. A First-Aid is a way to solve this while working on a release to everyone.
- Something users must request via the Extension Details tab.
- This release is optional for the user to download.
- Can be a fix for an issue that only happens for a small group of users.
Often used to test in an isolated group of users before the solution is rolled out to a larger group of users
Comments
0 comments
Please sign in to leave a comment.