It is a shame that it has become the new practice and/or philosophy of the various module teams to completely ignore these types of questions. While I understand that they don't want to commit to a certain schedule, I think it is very disrespectful to completely ignore simple requests for updates or even update the module project blogs. This also happens with the gallery module by the way. And please don't tell me that development is done by volunteers and that I should get involved to get things fixed. I thought that after the DNN effort became backed by a newly formed corporation that we could take this development more seriously, the situation has become worse. We, the guys (and gals) in the trenches, are recommending DNN for serious solutions for business and government environments worldwide. We are the lifeblood of DNN and we deserve and demand to have regular updates so that we can make our plans too.
IMHO, the core team, and most likely the different module teams, have become so involved in managing the development of major architectural changes that reliability, productivity, and communications suffer. Take for instance the problem with missing DLLs in the last release, not only that is bad enough, but no corrective action was ever taken. They don't even care about bad PR any more. This to me is difficult to comprehend, I can only conclude that there are major problems going on internally in the DNN "Corporation".
DNN Corporation, please communicate with us, your loyal user community. I would even go so far as to suggest that ALL module teams should make a blog entry with status reports AT LEAST once a month. You don't have to make schedule promises or anything, just let us know that you are alive and that the projects are moving along. I think we have demonstrated PLENTY of patience.
Sincerely,
Carlos R. Rodriguez
A loyal DNN evangelist since version 1.x