While I was away at TechEd, one of the news items at Telerik was the official publication of the Telerik RadControls Support Lifecycle (or TRSL for short). Similar to Microsoft's Support Lifecycle policies, the TRSL aims to give developers (you) a very clear and transparent plan for how Telerik will support "old" versions of its software. With this information, there should be no surprises regarding when support for an old framework version ends. You should be able to make plans well in advance of a product's "sunset" date and make the necessary arrangements to upgrade your projects as necessary.
This policy formalizes what has been the general practice up to this point at Telerik. With .NET 1.x increasingly less common, though, and .NET 3.5 just around the corner we thought it was very important to make it clear how we will transition our support for these different framework versions. We've tried to make things as clear as possible on the policy page, but if we've missed something please don't hesitate to contact us for clarification.
We look forward to helping you leverage all of the latest technologies Microsoft has to offer and to helping you support your existing applications. Hopefully this policy will help make it clear exactly how we will try to achieve that balance.
3 comments:
Thanks for the heads up. I'm curious though as on the graph that is posted, they use Q1 or Q?. Does that have any relation to the releases titled with Q1 or Q2 that really aren't quarterly releases? Am I making sense because I'm really confused ;)
Nick-
Sorry for the confusion. The "Q" tags on the graph are indeed tied to the Telerik "Q" releases (of which there are now 3 per year). So, anytime you see "Q1" or "Q2" in terms of a telerik release, think of it as "Release 1", "Release 2", etc.
Does that help clear things up?
Thanks~
Todd
Yes, that indeed cleared it up for me. Thanks.
Post a Comment