Learn More





DNN Community Blog

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Cambrian News...

With anticipation building for the next generation DotNetNuke platform, as well as some general misconceptions circulating in the community, it is important to clarify some of the most important details around the impending arrival of Cambrian.

When the Cambrian plans were first announced at the OpenForce conferences in late 2007, it generated a great deal of excitement within the DotNetNuke community. The Cambrian roadmap identified a number of large scale enhancements to the DotNetNuke product, features that have been requested by various members of the community for quite some time, and which will no doubt significantly accelerate business adoption of the platform.

Although we often refer to the next generation DotNetNuke platform as the Cambrian "release", it was never intended to be a single monolithic release. Rather, as per our standard iterative development methodology, Cambrian is intended to be a series of major software releases, each containing significant new functionality and upgrade support from previous versions. The iterative approach allows us to focus on delivering specific enhancements to the community, obtaining valuable feedback, and stabilizing the product; all in very short release cycles.

The goals of Cambrian are fairly ambitious, and due to the size and scope of the work involved, are contingent upon at least one major contributing factor. Enhancements of the magnitude being contemplated require dedicated resources. I covered this topic in some detail in the first chapter of the DotNetNuke 4 book from WROX but to summarize, the widely shared notion that open source projects basically have unlimited resources at their immediate disposal is not based on reality. Now, I am not disputing the cost benefit of the open source model, as it is now a well established economic fact. However, what is not so well understood, is that not every available resource has the precise expertise required, nor can they be counted on to contruct the software in accordance to the vision or goals of the project founders, or on the desired schedule. To put this into perspective, it is similar to putting out an invitation for any stranger who owns a hammer to come over and build a portion of your new house. Now, I am sure you would end up with some type of shelter, but I am not so sure if the end result would meet your expectations of quality.

When we announced the Cambrian roadmap, we knew that resources were going to be a challenge. Serious development requires significant financial resources and to deliver the Cambrian functionality on the estimated schedule, we knew that we would need to acquire some sufficient sources of funding. Since late 2007 we have been pursuing funding from professional and institutional sources, but the results are taking longer than expected to materialize. As a result, although the scope for Cambrian has remained the same, the schedule has slipped slightly from our original plan. The original schedule included quarterly milestones aligned with each of the significant enhancement areas of the Cambrian roadmap; with the entire product offering to be delivered by the end of 2008. At this point we anticipate the schedule has slipped one quarter; although we feel that it is possible that we could achieve the original milestones if sufficent funding is confirmed in the immediate future.

Moving on to some of the specific details around Cambrian, its important to clarify one of the false assumptions which I have heard in the community in recent months. At this point, there are no concrete plans to introduce breaking changes as part of Cambrian. As a framework, we recognize the vital importance of maintaining backward compatibility with third party solutions and as a result we always try to introduce new functionality in a non-breaking manner. This is especially true as the business ecosystem evolves around DotNetNuke; as it makes no business sense for us to provide a barrier which restricts users of the platform from upgrading to Cambrian. Now, to be honest, there are sometimes scenarios where there is no practical solution which will allow us to maintain compatibility. In these cases, we always consider the number of users affected by the change, and will only proceed if the issue is isolated to edge conditions so that the conventional use cases are unaffected. As an extra precaution, we plan to work closely with module developers and skin designers to ensure we catch compatibility issues early and provide them with a chance to get prepared for the new platform ( DotNetNuke Marketplace vendors will be given first priority ).

In regards to the Cambrian roadmap, it is important to note that most of the enhancements identified previously ( ie. in my OpenForce keynote ) belong in the content management category. Enhancements such as social networking, workflow, user interface overhaul, etc... are critical to business usage scenarios and will have a large impact on platform adoption. However, before we could proceed with these enhancements, some major foundational modifications were required to the underlying web application framework in order to facilitate the content management functionality. As a result, the initial Cambrian release will not contain any of the marquee enhancements identified on the roadmap. Instead, it will contain infrastructure enhancements which provide a solid foundation for implementing the content management enhancements in future releases.

We are now 5 months into Cambrian development and are near feature complete on the initial 5.0.0 release. There are a sigificant number of framework enhancements which are already integrated and will definitely need to be described in more detail in order to comprehend their true business or technical relevance. You can expect a Beta drop in the coming weeks. I hope the community is as excited about Cambrian as I am; 2008 is going to be huge year for DotNetNuke.


Comment Form

Only registered users may post comments.


2sic Daniel Mettler (124)
Aderson Oliveira (15)
Alec Whittington (11)
Alex Shirley (10)
Andrew Nurse (30)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (21)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (203)
Chris Paterra (55)
Clinton Patterson (28)
Cuong Dang (21)
Daniel Bartholomew (2)
Dave Buckner (2)
David Poindexter (3)
David Rodriguez (2)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (74)
Geoff Barlow (6)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (269)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matthias Schlomann (15)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Mike Horton (19)
Mitchel Sellers (28)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Peter Donker (52)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott S (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (2)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (37)
Will Strohl (163)
William Severance (5)
Try Evoq
For Free
Start Free Trial
a Demo
See Evoq Live
Need More Information?