To clarify, DotNetNuke.com IS using the latest version... 3.2.2/4.0.2 are simultaneous releases supporting two different versions of the .Net platform.  There are a number of simple explanations for why we are running 3.2.2 rather than 4.0.2 at the moment.

• Resource constraints.  We have quite a number of activities in progress and upgrading the www.dotnetnuke.com site to ASP.Net 2.0 has not reached the top of the todo list yet.  You may note, however, that we do have several other non-public sites running version 4.0.2.
  
• Commitment to the 3.x series.  Prior to the ASP.Net 2.0 rollout, there was ( and continues to be ) a lot of questions about our commitment to supporting the 3.x codebase.  We've made exceptional efforts to demonstrate our commitment to this and upgrading the site only to 3.2.2 rather than to 4.0 at the time of release was a conscious decision.

It's not likely that we'll take the time to do the ASP.Net 2.0 upgrade ( and thus the 4.x upgrade ) until the next release.

Version 3.2.2 and 4.0.2 are functionally equivalent.

* It should be noted that version 4.0.3 was released specifically to deal with a caching issue isolated to the ASP.Net 2.0 platform.

Scott Willhite, Co-Founder & Director of Community Programs for DotNetNuke

Let me just tell you my experience with DNN 3x and DNN 4x.

I have a Windows 2000 server IIS 5 with SQL 2000, low end machine.

I had a DNN4x site up and it was horribly buggy for me.  I was constantly having to reload pages to get them to render.  I finally desided that my enviroment just wasn't going to work with the 2.0 Framework.  In general though I tend to be a late adopter on most things.

Stuart