So rare in fact that if you look at the failed projects, over time... around 300 submissions to the tracker have failed :).

> Too many modules fail out of the tracker for me to believe that those teams are doing proper pretesting before submission.

So we hope the tracker actually encourages pretesting within projects, otherwise projects would fail more regularly. Remember development of these modules are done with teams littered all around the world, we can't just hover over team leaders shoulders and tell them how to manage their own projects.... nor would they want us to..... but we can test the results of their excellent work so it is of a common standard, which will allow them to learn next time how not to fail a project in the tracker. The process can be iterative.

This is a problem with many of the projects and has been for a long time.  We all appreciate what the volunteers do and I'm sure we have no idea how hard many of them work. 

However, DNN is in the big leagues and 'real' sites run on it and these sites are important to the owners.  DNN is not just for hardcore programmers (that can fix the bugs) or hobbyist (that can live with them) any more.

DNN Corp must simply decide that for 'official' projects there will be rapid bug fixes and frequent point releases for stabilization.  If that can't occur then announce the end of that particular module's project and donate the code so 'for profit' developers can sell non-opensource modules from it.  In other words, offer professional quality module support in the base or drop them to focus efforts elsewhere.

I personally use ActiveForums from activemodules.com (no I don't work for them :).  They have great support and release bug fixes rapidly.  Their product is very affordable.  This is a huge benefit with DNN that we have the commercial ecosystem around the product that fills in gaps.  Not everything can be free :-)

More time? In all fairness that has been the ongoing song and dance for at least a year now. I am sorry to say but that well has gone dry. It seems to me personal feelings, friendships are driving this project more then common sense and good mgt skills. As someone who has no attachment to any of the team on this module I would, if up to me, can them and get some dedicated folks who have the time. Nothing personal, simply strait forward mgt 101 skills.

Clearly a new team is needed and 2 years between updates with outstanding bugs almost as long should be unacceptable by any standards. I would ask those in change to put personal bias aside and look at this from a 'whats best for the project' point of view. Not 'whos my friend' or 'loyality' factor.

My 2 coppers