OK it didn't but it might have as well after spending 2 hours last night manually installing tens of legacy skins and containers and clicking and clicking and clicking and taking breaks to give my arm a rest. Each skin requires like 6 clicks.

The batch skin installer in DNN 5.0.1 is broken. It doesn't work. I have reported this issue in DNN 5.0.0. In DNN 5.0.0 I used a tool called RespackSkin which repackaged the legacy skin. I don't know but it seems the installer in DNN 5.0.1 is broken in a different way because RepackSkin didn't help. The only way tto install a legacy skin is to do manually.

I have some questions:

- Why weren't there beta's or release candidates released for 5.0.1? I could have caught this bug.

- Are unit tests being used? Are there plans to use them?

- Why aren't the change sets released on CodePlex? Will Strohl in another thread said it's for security and stability reasons. What does that mean exactly? How is giving the public  a way to test new changes and bug fixes affect security?

If the DNN testers aren't able to Submittest every functionality of DNN, let the public join in. What's the harm in that? All the open source software I use allow betas to be downloaded.

The bug was reported already by someone else and you reported that already just a few days ago!

http://www.dotnetnuke.com/Community/Forums/tabid/795/forumid/108/threadid/291688/scope/posts/Default.aspx

Yes Alex I can give a b/w answer. Release the bug fixes as you go so people can test quickly. This is continuous testing. You release a bug fix today, I can test it, I report it's still broken and the developer can fix quickly and so on. It's an iterative process. Can you see that this process is more efficient than fixing a bunch of bugs, do an official release and we get the same broken bugs and then wait for maybe two more months for the next release. I find it silly that the same bugs are carried over to new releases. I am not talking about bugs that had no time to be fixed but the ones that are reported fixed but weren't. Plus a handful of testers can never match the testing power of thousands of volunteers.

I don't want to use 4.x. I am starting with 5.x fresh. The new platform is my starting point. I don't want to go through upgrade issues that many people are reporting.

What do you mean by "should you have evaled 5.0.1 a little more carefully?". I reported the defect because I am evaluating it!

So you are a DNN tester who tests AFTER a release and not before? Let me ask you this, are you just like one of us or do you have more access?

And I am not gettting a straight answer: why are there no release candidates or betas or access to change sets on CodePlex?

Obviously you're not in the same boat. My specific argument is why aren't the betas made public?  You talk about Gemeni and who does the fixes and go into side topics. A few developers work on fixes. What does this have to do with my question?