After 8 months of effort the finish line is in sight. With almost 3000 code checkins touching more than 2000 individual files, this release has been monumental in it’s scope compared to most DotNetNuke releases. Not since the days of DotNetNuke 2.0 and 3.0 have we accomplished so much in a single release. In spite of the sheer number of changes we have made, DotNetNuke 6 is one of the most stable platform versions in quite a while. That is not just my opinion but the opinion of the vast majority of people participating in our beta testing.

Blog 4.1.0

This past weekend a new DotNetNuke Blog release candidate was posted on CodePlex.  This version of the blog addressed several longstanding issues with the Blog module and should be the final Release Candidate prior to the official release.  In 4.1.0 we really focused on fixing some of the biggest problems with 4.0 and doing some security hardening based on feedback from our security team.  In addition we added support for custom JS and CSS and temporarily removed support for Twitter (we’ll be bringing back an improved Twitter option in the next release).

One of the features that I was really excited about including in this release was the ability to support code formatting in the blog module.  There are many different methods that I have used over the last several years to format code in my blog posts.  The common denominator in every case is that it generally required me to add some custom JavaScript and CSS in the blog post so that it could be displayed properly.  In addition to code formatting, we also wanted to support the ability of administrators to include their own CSS to override defaults.

Earlier today, DotNetNuke hit another milestone with the release of DotNetNuke 5.0.0 RC1.  RC1 is our first stable DotNetNuke 5.0.0 release and represents a feature complete version of the 5.0 platform.  From here on out we will be focused on fixing bugs and ensuring that any performance issues are resolved.  While it is true that DotNetNuke 5.0 represents a substantial change from 4.8.x, many of the updates in 5.0 were back ported to the recent 4.9 release.  Below is list of highlights for this release which were not included in 4.9.0.

Major Highlights Added jQuery support to the core platform.  jQuery will now be distributed as part of the DotNetNuke installation and will be available for use by module developers. Added support for...

We are in the final stretch for the 4.9.0 release.  This release was originally going to be the 4.8.5 security release, however, given our slippage on DNN 5.0 we decided to backport a few critical fixes for the 4.x platform and felt that this was a good time to do that.  We think that 4.9 will provide a stable platform for everyone wishing to remain on the 4.x codebase for a while after 5.0 is released. [more]

Major Highlights Fixed issues with the URL Rewriter.  There were several issues which could result in unreachable pages using friendly URLs.  We have added in validation logic to prevent pages from being created which would violate folder naming standards or which would result in two pages receiving the same Human Friendly URL. ...

DotNetNuke 4.6.0 is quickly approaching the release date.  We have gone through 2 different beta releases and have now packaged and release RC1 to our testers and benefactors.  While we have implemented a new beta testing group and added more default test cases into our test tracker, we are still not getting the level of testing that we feel is necessary.  We had a lot of people sign up for the beta test who ended up not being active participants which really hurt our testing efforts.  Out of nearly 60 people accepted into the program, fewer than 1/3 actually contributed feedback on the quality of the release.  We will continue to open up beta...

This weekend, DotNetNuke 4.5.4 was released to benefactors for final release testing.  4.5.4 is primarily a stabilization release with just a few key enhancements and one new feature.

The final release date has not been announced pending the results of testing by the benefactors and core team.  As part of this release we have started implementing new processes to help improve the stability of each release.  We still have a lot of work to do, but this marks the first step in refining the process.

 

 

 

Component Issue Type Issue ID...