We try to stay fairly current. Progress adds features and bug fixes with every release. I have, at least a half a dozen times, had bugs where the ultimate fix was to upgrade the Kendo. In addition, the upgrades isolate you from having to deal with other issues, like browser changes.
That said, the first release this year felt like a gut punch. The controls were changed to use new styling classes and in some cases a new DOM architecture, breaking our code on almost every page. Worse, the release seemed to introduce a whole bunch of new bugs.
Progress quickly responded with a new version which just came out a day or two ago, but upgrading to this version is going to require a bunch or reworking of our CSS and Javascript.
We try to stay fairly current. Progress adds features and bug fixes with every release. I have, at least a half a dozen times, had bugs where the ultimate fix was to upgrade the Kendo. In addition, the upgrades isolate you from having to deal with other issues, like browser changes.
That said, the first release this year felt like a gut punch. The controls were changed to use new styling classes and in some cases a new DOM architecture, breaking our code on almost every page. Worse, the release seemed to introduce a whole bunch of new bugs.
Progress quickly responded with a new version which just came out a day or two ago, but upgrading to this version is going to require a bunch or reworking of our CSS and Javascript.
See https://docs.telerik.com/aspnet-mvc/styles-and-layout/components-rendering-overview#what-is-the-reason-behind-these-changes