Thanks for replying Dario,

As it stands, the blog package is five years behind every other blog package out there. 

We either need something better.  Our options are:

• get the new version of the official blog package, which has been stalled since July (?) because of trivial testing problems (2 cols need to be switched to nvarachar...that's it?)
• get the source and modify it 
• move to something else entirely. 

Right now, #2 looks like the best option, but there is no download available on the project page for the 3.05 release candidate source, and over on sourceforge, the CVS repo looks empty.  What gives?

If this is an open source project, why can't I get the pre-release branch?  

Hi All,

@Jeff: thanks for the support, I bet you will be nicely suprised by the new version, and your users will appreciate the MetaWebLog support.

@Brian: I agree with you that an open source community should have less restrictive release policies. But, as I told before, the Core is betting much on security and quality to make DNN a reliable platform for enterprise solutions on the Net. On the other hand this may cause many skilled developers to keep out, without being actively involved. The Blog module has some delay from other solutions on this framework, but during the last weeks the team earned some of the most skilled and expert developers in content publishing. The next generation module will be entirely rewritten, and we expect that it will compete with the most professional publishing solutions.

@Everybody: I think that Core Team Members have to deal between the openness of the comunity and meeting high quality standards. This is not easy, but contribution is always needed, even criticism, because it helps us understand what's wrong.

Best regards,
Dario Rossa

I dont see it in the release tracker.  The last one I see is on 8/12/08 failed for SQL localization.  After that I do not see any updated version.  It is now over a month later and there is still nothing in the release tracker.

Dario Rossa wrote   Hi Mike, the first submission to the release tracker failed because of an unneeded file in the package. The module has been resubmitted, and will be released as soon as it passes all the steps in the release tracker. Since this new version includes so many enhancements, we hope this will take not too much time. Best regards, Dario Rossa