Another possible solution would be to open up a read-only SVN repository. Benefits:

People would be able to see active progress on the code
Impatient developers could roll out code changes incrementally, instead of having to wait for the next release
Upgrading could be as simple as "svn up"

Has the use of a SVN repository been discussed? I'd be interested to hear other reasons for/against it.

On a side note, I'd have to agree with one of the previous replies that stated that
Moderation on this board should be turned off.

It's more than annoying when you're trying to help somebody, but since they are new their posts don't show up for extended periods of time. I've seen the argument that moderation allows the moderating team to actively answer their questions. I'd argue that at any given time the number of non-moderators able to answer the question will likely outweigh the moderators. Don't get me wrong, I appreciate it when the moderators / core team do answer questions.

For the uninitiated, it appears that there is a disconnect between the forum and its users. I know when I first joined, I was getting frustrated that I wasn't able to get or give instant feedback. I'm sure others have felt the same way.

I'd be interested to hear the developers' thoughts on this one as well. Thanks.

I agree, John. I had considered the benefactor program when I was originally mulling over the idea, and came to the same conclusion. Benefactors should get the better support.

I was thinking about something else- if this has been addressed already, forgive me. I don't know if the upcoming release tracker is going to tackle this issue.

The DNN Core Framework project on Gemini should use the Roadmap functionality. Right now it's a fairly limited roadmap- only items for the next release are assigned to it.

Why not start setting milestones? Make a 4.5.5 category. A 4.6.0 category. A 5.0 category.

Right now it appears that there are over 800 bugs just floating in the ether. Will they be addressed? When will they be addressed? What is their true priority? Nobody knows.

I'm not sure if there's some kind of internal method that's used for determining what features to focus on- but from my viewpoint it appears that the developers address random (or important) issues.

I know about the feature voting page, but that is limited in scope.