We tried yesterday to upgrade to latest version of Telerik (2011.2.712) an noticed that it does seem to break encoding for the buttons generated for each row (Edit) etc. Has there been any changes with regards to this compared to the 2011.1.413 which we used before??
We use recource files for localization to Swedish and for edit we have "Öppna" which displayed fine until we started using 2011.2.712, now it is displayed as "Öppna". When we rolled back to 2011.1.413 DLL it is displayed correctly again.
Any ideas?
We use recource files for localization to Swedish and for edit we have "Öppna" which displayed fine until we started using 2011.2.712, now it is displayed as "Öppna". When we rolled back to 2011.1.413 DLL it is displayed correctly again.
Any ideas?
5 Answers, 1 is accepted
0
Hello Patrik,
Indeed, this problem exists in our latest official release. It is already fixed by our developers and you can try the latest internal build for a hotfix. Please excuse us for the caused inconvenience.
Kind regards,
Pavel
the Telerik team
Indeed, this problem exists in our latest official release. It is already fixed by our developers and you can try the latest internal build for a hotfix. Please excuse us for the caused inconvenience.
Kind regards,
Pavel
the Telerik team
Browse the vast support resources we have to jump start your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
improwise
Top achievements
Rank 1
Iron
Iron
Rank 1
Iron
Iron
answered on 11 Aug 2011, 10:57 AM
How do you communicate to customers about know stopping faults discovered in your products? For us, this is considered a stopping fault and we were lucky that we caught it in our own testing. I'm guessing that there might be customers out there who are affected by this or other known serious problems, without even knowing it.
I must say that I am a bit worried about the Quality Assurance process at Telerik as this is the 3rd or 4th time only last year that we have upgraded to the latest version only to find that it has problem so serious that we have had to roll back to previous version, and that we think should never have made it trough the QA process. How come the latest version isn't pulled back or replaced with a working version when such a serious problem is discovered, or at least marked with a "CAUTION" flag?
I don't really understand the concept of internal versions and how they are supposed to be used by us customers? We are running a mission critical application (internet banking) and would never dream of putting anything that isn't officially released and supported into our production environment. You mention this yourself with regards to internal releases as "intended for development only" and "not recommended for production purposes"
My conclusion is that even a month after 2011.2.712 was released, it is still not usable for any international users using resourec files and that there exist no official hotfix/patch for it, am I correct?
Sorry for being so hard on you but this is frustrating and we are having concerns about implementing new version of the Telerik controls, without doing a lot of testing at our end that we think should have been done at your end.
I must say that I am a bit worried about the Quality Assurance process at Telerik as this is the 3rd or 4th time only last year that we have upgraded to the latest version only to find that it has problem so serious that we have had to roll back to previous version, and that we think should never have made it trough the QA process. How come the latest version isn't pulled back or replaced with a working version when such a serious problem is discovered, or at least marked with a "CAUTION" flag?
I don't really understand the concept of internal versions and how they are supposed to be used by us customers? We are running a mission critical application (internet banking) and would never dream of putting anything that isn't officially released and supported into our production environment. You mention this yourself with regards to internal releases as "intended for development only" and "not recommended for production purposes"
My conclusion is that even a month after 2011.2.712 was released, it is still not usable for any international users using resourec files and that there exist no official hotfix/patch for it, am I correct?
Sorry for being so hard on you but this is frustrating and we are having concerns about implementing new version of the Telerik controls, without doing a lot of testing at our end that we think should have been done at your end.
0
Hi Patrik,
I understand your concern - in this particular case the problem slipped through our QA process, as it was affecting some culture-specific symbols, which were not covered by our automated tests. We apologize for this omission on our part. I can assure you, we have taken the necessary measures to include these cases in our regression tests.
I also understand that this information does not help you solve the problem and actually use the latest official release in your production. Unfortunately we are planning a Service Pack for the mid of September, which means that, since you are heavily affected by this issue, you will have to use an older version of the controls until then. We will consider whether releasing a single Service Pack is viable option in cases like this and shouldn't our release schedule be more flexible.
The only thing I can suggest you, however risky it may seem, is to try the internal build which will be uploaded today (it will include a few more fixes which affect the Grid in similar scenarios) and if it passes your internal testing - use it in your production. As a further information I can give you, I have consulted with our QAs which have tested the controls with our last nightly build, and there should not be any major issues with them (and RadGrid specifically).
I hope this helps, and please accept our sincere apologies once more.
All the best,
Pavel
the Telerik team
I understand your concern - in this particular case the problem slipped through our QA process, as it was affecting some culture-specific symbols, which were not covered by our automated tests. We apologize for this omission on our part. I can assure you, we have taken the necessary measures to include these cases in our regression tests.
I also understand that this information does not help you solve the problem and actually use the latest official release in your production. Unfortunately we are planning a Service Pack for the mid of September, which means that, since you are heavily affected by this issue, you will have to use an older version of the controls until then. We will consider whether releasing a single Service Pack is viable option in cases like this and shouldn't our release schedule be more flexible.
The only thing I can suggest you, however risky it may seem, is to try the internal build which will be uploaded today (it will include a few more fixes which affect the Grid in similar scenarios) and if it passes your internal testing - use it in your production. As a further information I can give you, I have consulted with our QAs which have tested the controls with our last nightly build, and there should not be any major issues with them (and RadGrid specifically).
I hope this helps, and please accept our sincere apologies once more.
All the best,
Pavel
the Telerik team
Browse the vast support resources we have to jump start your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.
0
improwise
Top achievements
Rank 1
Iron
Iron
Rank 1
Iron
Iron
answered on 12 Aug 2011, 12:33 PM
First of all, let me thank you for your very profesional response to my post. It could have been very easy to go into defensive positions but instead you chosed to give a very good response to this and a clear understanding of the situation. That is worth an extra gold star in our book.
I still feel you need to improve your QA process though, as this is not the first time a similar error has slipped through. That said, I should point out that we know how difficult it would be in real life to find all possible bugs in a release without months of intensive testing, which may not be an option when we customers expect frequent releases as well.
What you however should do is to find a better way to handle serious problems in current releases once they are known. It is not ok that we were very close to putting a new Telerik release into our production environment which had serious problems that were known before we even downloaded it. Depending on the situation, I think that the release should either have been removed or at least labeled with a clear warning message. Also, it would be nice if you could send out "alerts" in case serious problems are found in a current release (this might already be available just that we dont know about it).
Thank you again for responding to this in a profesional way.
I still feel you need to improve your QA process though, as this is not the first time a similar error has slipped through. That said, I should point out that we know how difficult it would be in real life to find all possible bugs in a release without months of intensive testing, which may not be an option when we customers expect frequent releases as well.
What you however should do is to find a better way to handle serious problems in current releases once they are known. It is not ok that we were very close to putting a new Telerik release into our production environment which had serious problems that were known before we even downloaded it. Depending on the situation, I think that the release should either have been removed or at least labeled with a clear warning message. Also, it would be nice if you could send out "alerts" in case serious problems are found in a current release (this might already be available just that we dont know about it).
Thank you again for responding to this in a profesional way.
0
Hello Patrik,
Your case has been escalated to me and I certainly understand your concerns - this is exactly how I feel when I discover a bug in a software product which directly affects its usage in my scenario. We are cumulatively increasing the (already) large set of automated test that are run with each release, and on top of that invest in manual testing power to verify that we cover as much of the object model and functionality of our controls as possible.
However as you concluded, in the real life you can very seldom dedicate weeks for testing purposes only, without any dev check-ins, and there is always a possibility that an issue might slip through our QA engine. This is surely unpleasant and we do everything possible to react adequately.
Fortunately, for this purpose we do release internal builds each week (two times per weeks sometimes) which address reported issues/bugs that can hinder our clients development process. In addition to that, from now on, we intend to post an unofficial hotfix build in a sticky forum thread (when necessary) which incorporates all recent fixes and passed successfully our automated and manual tests. This will happen when the next official service pack release is ahead in the future and there is a necessity from a temporary solution which can be used in a production environment.
I truly hope that this will strengthen your faith in our AJAX components and will make the upgrades to future releases more seamless and stress-free.
Regards,
Stefan Rahnev,
Telerik Unit Manager, ASP.NET division
Your case has been escalated to me and I certainly understand your concerns - this is exactly how I feel when I discover a bug in a software product which directly affects its usage in my scenario. We are cumulatively increasing the (already) large set of automated test that are run with each release, and on top of that invest in manual testing power to verify that we cover as much of the object model and functionality of our controls as possible.
However as you concluded, in the real life you can very seldom dedicate weeks for testing purposes only, without any dev check-ins, and there is always a possibility that an issue might slip through our QA engine. This is surely unpleasant and we do everything possible to react adequately.
Fortunately, for this purpose we do release internal builds each week (two times per weeks sometimes) which address reported issues/bugs that can hinder our clients development process. In addition to that, from now on, we intend to post an unofficial hotfix build in a sticky forum thread (when necessary) which incorporates all recent fixes and passed successfully our automated and manual tests. This will happen when the next official service pack release is ahead in the future and there is a necessity from a temporary solution which can be used in a production environment.
I truly hope that this will strengthen your faith in our AJAX components and will make the upgrades to future releases more seamless and stress-free.
Regards,
Stefan Rahnev,
Telerik Unit Manager, ASP.NET division
Browse the vast support resources we have to jump start your development with RadControls for ASP.NET AJAX. See how to integrate our AJAX controls seamlessly in SharePoint 2007/2010 visiting our common SharePoint portal.