Allen,

main advantage of a formalized process is to decouple tasks, that are taken out by multiple persons. As I told you, we are continuosly improving our processes, which is necessary - and often not avoidable in growing organizations like DotNetNuke. One step in this process, taken about 2 years ago, was to separate the modules from the core and hand over responsibility to individual teams. Though most of the modules are still bundled with the core framework, they are developed independently with the teams own release cycle - now followed by a formal release tracking process to ensure common guidelines and quality.

Each team is trying to get the best out of its available resources and so do we. Since the UDT team started (with only 2 persons at that time), we issued a number of released, significantly improving this valuable module (compare it with a UDT 3.1.0 release, that has not changed since DNN 1). When Stefan entered the team, he did a great job in refactoring the code and adding XML support, .... 

The next release of UDT will be another large jump ahead. We completely reworked the ManageUDT area, added a bunch of options while trying to keep handling even more simple and intuitive as it has been before, even leveraging (does this word exist?) the use of XSL which gives you most flexibility in formatting the display of the list. IMO the greatest improvements will be filter and search options. Due to this number of enhancements and new features, developement needs its time - we are close to finishing development phasis, which needs to be followed by alpha testing and documentation, before the module can be packaged and submitted to the release tracker. After a module passed the Q&A-Team, it gets beta-tested by the core team, team leads and platinum benefactors, before it will be officially published.

As I am also spending some time to support users in the forum, provide hundreds of German language packs and are currently busy with forming a German DNN user group - I ask you to be patient, if not every desire can be fulfilled in a second.

Sebastian don't try to spin this issues into something is is not. I am not inpatient, I am not complaining about the quality of the product. I think the product is awesome and you guys work very hard, but for some reason you are stuck on this process issue.

As you pointed out the process failed for me in this case. All I have done is elaborate on my perceptions and ask a simple question when do you think a fix will be available, this is not an unreasonable request given that it has been "fixed" in development since October. but after multiple post you won't answer that question. As least say I don't know, but I am sure you can do better (e.g. At least 3 week or 3 months etc...)

Allen,

the module gets submitted to the release tracking process, when it should be released: when it is ready. I already stated during the past week, that this is planned within the next two weeks - but there is still some risk for a delay due to the fact that I will participating in MVP summit and have to prepare (and execute) presentations of DotNetNuke at CeBIT trade fair. Please also consider the release process to take several weeks needed for testing etc. by the core team, before the module gets to the beta testers and finally to the public. As this shall be the last feature release for DNN3, it is my aim to release a feature rich module with good usability.

Again, please note, that module release cycles are decoupled from core release cycles and accept, that our resources do not allow us to provide additional releases like you mentioned.

Take this as mi final answer, I close this thread, amen.