This article provides information on the provided support for earlier Telerik UI for ASP.NET MVC versions.
The support policy includes the way bug fixes, feature enhancements, and browser compatibility are updated and applied across the Progress® Kendo® UI for jQuery, Progress® Telerik® UI for ASP.NET MVC, Progress® Telerik® UI for ASP.NET Core, Progress® Telerik® UI for JSP, and Progress® Telerik® UI for PHP suites.
For best performance results, use the latest Telerik UI for ASP.NET MVC versions which contain all recent features and fixes that are available.
Bugs in Telerik UI for ASP.NET MVC helpers or the Kendo UI for jQuery widgets they wrap are fixed depending on the priority set by the product management and based on the public Feedback Portal, support system, surveys, interviews, and other means at management discretion.
Bug fixes are then implemented in the product by the Development team and later introduced in the first official product release. Internal (nightly) builds may also contain bug fixes before an official release is available and you can use them to keep developing your application. However, avoid promoting them to production.
To get a bug fix, you have to upgrade your project to the same release as the release that contains the fix, or later. For more information, refer to Downloading New Versions.
If a workaround for an earlier version is technically feasible, you may be provided with such in the ticketing system. However, Progress Software Corporation cannot guarantee that bug fixes in earlier versions will be available and cannot give warranty for any workarounds that are provided.
Feature enhancements and new helpers become publicly available in the first major release and after their implementation by the Development team.
New features and helpers are not available for versions which come before the first version in which they were released.
Telerik UI for ASP.NET MVC versions support only browsers that were available at the time of their release.
For earlier versions, you can get suggestions on how to implement certain scenarios and features in your project in the ticketing system and depending on their technical feasibility. If such an implementation relies on the API, fixes, or enhancements that are implemented in later versions, you will need to upgrade to a release which contains the feature you need.