As I indicated last week, I am pleased to announce the Call for Speakers for the 2010 DotNetNuke Connections conference.  Once again, this years conference will be held at the Mandalay Bay in Las Vegas from November 1st through the 4th with pre and post-conference training available as well.  We could not do this show without our speakers and we have been fortunate in the past to have had some great session proposals by many well respected speakers.  Some of those speakers ha...

Over the past several months we have been making some significant changes in our release process.  We have made a commitment to monthly releases , opened up our code repository and in general have made a move to be more transparent.  During this same period we have also made some changes to our development processes to separate our feature development from our bug fixes.  The DotNetNuke 5.3.0 is our first quarterly feature release that is benefiting from this new development proc...

We are once again in the heart of the planning season for the DotNetNuke DevConnections and SDC conferences. It is that time of year when we ask all of you to submit your session abstracts for this years DotNetNuke North American conference.  Later this week we’ll be opening up the official Call for Speakers on DotNetNuke.com, but I wanted to take the opportunity to give speakers a heads up so they could start preparing their abstracts so that they are ready once we open ...

DotNetNuke recently moved to an Open Repository that is hosted on CodePlex.  As Phil Beadle recently noted , the synchronization process is now fully operational and is running nightly to ensure that the CodePlex repository mirrors our internal version control system.  Of course, having access to the source code and understanding how to use the source code to get to a working build is two different things.  The source code package that we deliver with each release is sli...

Over the last several years DotNetNuke has maintained a policy of providing an upgrade path for users running previous versions of the platform.  Only in rare instances will we intentionally break a feature or an API or do something that would cause 3rd party extensions to break.  Customers have expressed to us over the years how important it is to maintain an upgrade path.  This concept is not unique to DotNetNuke.  Various projects and companies will take a different stance on the t...

It has been a goal of the DNN project to be able to allow developers and anyone interested to download the latest source code from CodePlex without affecting our internal operations.  To do this I have created a CruiseControl.Net project that synchronises the source code in our internal system out to CodePlex on a daily basis.  If you check out the Source page for the project you will see the following today: Each time the source is updated by the CruideControl.Net project you will a...

  The automation tests now have the ability to test if an email was sent correctly.  To run the Email Configuration test you will need to update the “TestEmailPath” value to match the name of the subfolder you created eg  “D:\Tests\TestEmails” For the Email Configuration test you will need to add a file to the “Packages” folder. The file is called “mailDrop.xml” and is located in the “Support Files” folder within your project. Copy this file into your “Packages” folder. Open the xml file...

The DotNetNuke Automation Testing project is available on CodePlex at http://dotnetnukeautomation.codeplex.com/ and is welcoming testers and developers and anyone else who would like to contribute to try it out and write your won tests based on the style we have set up.  To get started you will need to set a few variables and create some folders.  Stefan did a nice post on it a few weeks back so this post is to add to that and explain a few differences.  In this example the tests will run t...

The Automation Test Project is well and truly underway now.  You can check out the progress we are making and the suite of tests that have been written to help with the Build Verification that now happens on every release here http://dotnetnukeautomation.codeplex.com/ .  These tests test a set of scenarios that we need to ensure work every release, hence they get executed on a very regular basis which is tedious if you have to do it manually every time.  If you check out the project you will s...

Another month, another DotNetNuke release.  With each passing month the Quality team continues to get better at building DotNetNuke in a repeatable manner.  Our processes are becoming more and more automated and our QA and maintenance teams are starting to become comfortable with the processes.  It is a marked change from where we were just 12 months ago.  As a stabilization release, we focused this month on closing out the highest profile issues in the issue tracker.  We continued ou...