We fix bugs on weekly basis and the fixes are released usually on Fridays two to four times per month. We refer to these releases as internal hotfix builds and they are incremental, meaning that the fixes in the latest internal build include all fixes from such previous builds. Our goal with these weekly hotfixes is to help customers and partners address important issues for specific use cases without having to wait for the next service pack or major product update.
The weekly hotfix builds are available to every customer who has access to the official product release that precedes them. The internal builds are available for download in your Telerik account and the release notes are posted in our forums where you can subscribe to get release notifications.
Every week our quality assurance team selects the bugs that are to be fixed for the upcoming bi-weekly build based on various criteria such as bug priority, complexity, and regression risk. The bi-weekly hotfix releases do not include breaking API changes, database changes and bug fixes with high regression risk.
7-Day Bug Fixing
Sitefinity Enterprise Edition customers can get their Severity 1 issues prioritized and fixed within 7 days. Sitefinity Team will attempt at resolving acknowledged Severity 1 product defects within 7 days. These fixes will be included in the bi-weekly internal hotfix builds, or delivered as patches, depending on the scheduling of the next bi-weekly internal hotfix build.
Due to some limitations like regression potential and necessary refactoring our service level objective (SLO) is to meet the 7-day target for 80% or more of Severity 1 product defects. Please note that the 7 days bug fixing SLO is provided for information purposes only and is not a legally binding commitment or agreement.
With the weekly hotfix builds we attempt at fixing all reported issues on top of the latest product version and we highly recommend that customers regularly upgrade in order to benefit from the continuous improvements. However, business conditions sometimes prevent customers from upgrading and in such cases we will attempt to prepare a patch on top of an older version. We can attempt to produce patches for up to one major version back from the current latest version (e.g. current major version 10.0, versions supported for patching are 9.0-10.0).
The produced patches are based on the latest internal hotfix build for your Sitefinity version. They have passed our fully automated test suite - which includes thousands of functional, integration, unit and performance tests. The actual bug fixes for which the patch is produced have also passed strict manual quality assurance and performance tests. These builds have not passed our full manual regression testing cycle that we do before each official release. "Silent" builds (ones that have been produced with the same Sitefinity build number as yours) are not supported - patches always come with an incremental build number so we can ensure proper maintenance of your project moving forward. The patch builds not include breaking API changes, database changes and high-regression potential changes or fixes, and upgrading to them should be seamless. Upgrade from these builds to the consecutive official release is fully supported.
This service is available only to Sitefinity Enterprise Edition customers. Please note that due to code refactoring it’s not always possible to apply a patch to an older version. Nevertheless, we stand committed to meeting your business needs and if it is not possible to produce a patch we will advise you on the best path to address the issue.
Testing and Validation
Every bug fix passes rigorous manual quality assurance and performance tests. Then, the internal hotfix build has to pass our fully automated test suite that includes thousands of functional, integration, unit and performance tests. However, these builds do not go through our full manual regression testing cycle that we do before each service pack or major product release.
Supported Upgrade Paths
- from an older official release to an internal hotfix taking into account our upgrade paths
- from one internal hotfix build to another as long as they are in between the same official releases
- from an internal hotfix build to the consecutive official release
Who should upgrade to an internal hotfix build?
We recommend upgrading to an internal hotfix build in case you experience the particular issues that were fixed and mentioned in the release notes of a given build. The internal hotfixes are production-ready and can be upgraded to the consecutive release or service pack at a later point in time. Otherwise, you don’t have to worry about these builds since all those fixes will be included in the next service pack or major product release.
How to submit product feedback and see what’s in the works?
Go to our feedback portal and if you don’t see an existing item that relates to your case, please share your feedback. As you browse the portal and see something that you would like us to prioritize, please give it a Like and feel free to comment. If you would like to receive status update and comment notifications, make sure that you follow the item. Alternatively, you can submit private inquiry from your Telerik account.