10 Nov 2004
02 May 2011
Link to this post
@Gabe, thanks for the update. This of course is the issue I've always had with the internal updates and now with the track record set by Telerik w/ the buggy 4.1 release. We can test all we want with this internal build, but if it's not a supported build what's the point, further more there's a really good chance that 4.2 (or 4.1 SP1) will introduce even more new bugs so we'd have to do our testing all over again. So really, to download this internal build, go through the process of upgrading is just a waste of time. Yes we may find that some of the 4.1 bugs are fixed but if they get broken again in the we've just gone in a big circle.
I think it's pretty obvious that the internal testing for Sitefinity is lacking, not for lack of effort but I think more because you just don't have all the scenarios available that your customer base is coming up with. I think you need to not worry about an internal build that can't be used, but getting a SP1 pre-release to us asap, and keep things attainable, don't try to fit in more than you can. Freeze the code, give it out to your customers to test for a week and if all is ok release as a stable build. I'm already concerned that the next SP is going to try to accomplish too much and is going to introduce new issues.
Baby steps... get your process dialed in and get our trust back!
Just my 2 cents...