You are correct, those loose guidelines are outlined. What should be happening is you should be thanking that it hasn't been released as I would say this is the most forward moving beta period we have ever had in a beta term. This obviously is helped by the Benefactors, but even more core teamers are contributing to finding and fixing issues as well. The changes that were made for this version were quite extensive and this is across two code bases. (1.1 and 2.0). I understand you want to see a new release but after discussion we decided to not release at the four week point to handle outstanding issues that were received via the feedback. To me, this is simple, if it takes another week to get it right then so be it as it is much better to be a week or two 'late' but solid instead of releasing with a set of bugs created by this new set of versions.

This is a no win situation overall with the community as some people don't mind the bugs as long as they get the release, but others want a solid release with minimal bugs and this seems to be the greater desire between the two.

 

---

Chris Paterra

Get direct answers to your questions in the Community Exchange.

As with most things, the truth/best option is somewhere in the middle. 

I myself have no problem with the platinum benefactors getting the preview they paid for--and am quite thankful they're willing to do the bleeding for the multiple builds during the beta period. While I certainly can debug the code, or wait for others to do so, this group is saving me from having to download, review, test, & install all those intermediates...

What I think could be handled better is the communication.  Sure projects run long, and some issues may NEED to be addressed prior to release--again thanks!  However the written expectation was given to the community of a 1-4 week beta period....if it takes longer, just give us a heads up and a revised estimate....then we'll know what to tell our customers and not look unprofessional ourselves...  No, I'm not asking for hard dates, I realize that is even more problematic and against a firmer DNN policy.  But why not a simple, proactive, statement that it'll be another 1,2, 3, or 4 weeks??? 

Simple ballpark estimates might head off a few cross threads, let everyone (Core Team, Project members, third party developers, hosters, and the rest of the community) look more professional--and ultimately avoid the hurt feelings that can make any member of that list question how much more they want to invest in DotNetNuke.

Please notice, that DNN does not have a release plan like Microsoft, so you can't count RC's. Testing phase is for discovering issues, that is what's going on and some of these issues are showstoppers, that needs to be fixed, before the version can be released. As far as I can see, the Core Team trie to release as quick as possible.

---

Cheers from Germany,
Sebastian Leupold

   

Speed up your DNN Websites with TurboDNN