I do commend Shaun, Joe, Mark, Vicenc, just to name a few of those who have been putting in tireless hours to push the release candidate through as soon as possible. Again, no set date, but I understand they are working on the Updating feature now as has always been the case of DotNetNuke is to provide an upgrade path to ensure that their project can be, as seamlessly as possible, upgraded.
This doesn't count for those custom modules of course, but I've heard several people do have their modules working in 3.07, and when 3.08 is released will be putting the final touches on to the modules for public release.
I did install the catalook store on 3.08 with not much luck, but wonder if it's because I hadn't turned off friendly urls. I run different servers and have a couple of glitches with the friendly urls.
Looking quickly through the forums, I noticed that there were a few common problems with 3.07 that I see have been rectified and feel now the consensus is that 3.08 is a good reliable and stable release. That's positive news as we move into the next generation of DotNetNuke and it also allows me to focus on the skinning aspect of my site.
I have had a few glitches with my own site and find it very very VERY annoying that some of the modules I have purchased or installed misbehave and have had to remove some becuase I'm a little bit concerned with how they affect the performance of the server.
Also, will be engaging an SQL expert to look at how I backup and maintain the databases so that I can document this and perhaps have some better tips in maintaining sites that get alot of traffic.
I've been doing so much thinking over the last few days on how I can push the information out and make people happy and today did a quick mind map of the process and what I think is important and will see how it pans out over the next week or so.
I believe most of the core team involved in this release will be back on deck from their holiday and family destinations, or offices like me (I have a cool home office) and making sure the upgrade path works as it should. This release is quite unique in how it's been written with the new methodology and processes in place, as developers would know by now and I think you'll find that when, and only when Shaun is happy with the outcome, we'll see a release come through. I think it's not overly far away- again, I never ask for more than I read about because the one thing people don't want to be, is disappointed with timelines that cannot be met due to things with code requiring updating.
With the core team working very well together, and a sense of achievement by us all (I am speaking blindly here, but believe it's fair to say) this release will exceed the expectation of many people because it's just so amazing.
What I will be doing though is looking after those who are still hooked on 2.1.2 for various reasons (custom modules is the only reason I can see) get the same look and feel for their sites should they like the look of DotNetNuke 3.
Thanks for tuning in – I'm spending the next few days on my stuff only – which is such a refreshing change and even though the payment gateway won't be finished, believe I have some cool ideas I can pass on.
Also, if you are a registered user, you'll see I've got another little survey happening – I want to know about Fluid versus Fixed (100% width versus 800 width) as I look at building the informaiton portal – Your opinion is appreciated.
Thanks and enjoy the festive season – Life moves by so quickly.
Nina Meiers