DotNetNuke 5.4.1 Released
Apr
28
Written by:
Joe Brinkman
4/28/2010 1:01 AM
I am happy to announce the release of DotNetNuke 5.4.1 which corrects the major issues which slipped through the QA process for 5.4. While we try to do a good job in testing our releases, our recent efforts for 5.3 and 5.4 have fallen short of the mark. We are currently working with a small team of commercial module developers and the core team to put a better public beta testing process in place that will help augment our own internal testing. Ultimately, community testing is the only testing that truly scales, and we have struggled with how to effectively use the community even while keeping to a tight release schedule. While this is not as critical for our stabilization releases where we seem to have no difficulty achieving an acceptable level of quality, it is absolutely essential that we have community feedback and testing of our quarterly feature releases. As usual, you can see the full list of changes for this release on the changelog.
Major Highlights
- Fixed issue with assembly version type.
- Fixed issue with multiple cancel buttons on Add User screen.
- Fixed issue with version number in Symbols package manifest.
- Fixed issue where system mails are sent from the recipient's email address instead of admin email address.
- Fixed issue with logo in Ribbon Bar.
- Fixed issue with race condition when adding entries to shared Dictionaries.
- Fixed issue with scheduler exceptions when more than one language is defined.
- Fixed issue when creating portals in non en-us culture.
- Fixed issue with adding a new language.
- Fixed issue with AJAX Script Manager
- Fixed issue with Source Package not opening correctly in Visual Studio.
- Fixed issue when logging into a multi-language portal when the user's preferred locale is not set.
- Fixed issue with generation of user links to use new Profile page.
- Updated version of Symbols package in manifest file.
- Improved 5.4.0 and 5.4.1 upgrade scripts to better handle upgrades when multiple languages are installed.
- Added label explaining portal localization drop-down on site settings. Updated static localization text to more friendly form.
- Added missing release notes for 5.4.
Security Fixes
Updated Modules/Providers
The following modules and providers have been updated in the 5.2.0 packages. Please see the specific project pages for notes on what bugs or enhancements were corrected with each release.
Modules
- Blog Module 04.00.00
- Form and List 05.01.03
Providers
1 comment(s) so far...
re: DotNetNuke 5.4.1 Released
Perhaps you should look at how Salesforce.com does things.
In Salesforce.com, anyone can write "Apex" code and add it to their cloud Salesforce.com instance.
However, before you can move your code from your sandbox to your live environment, you have to write a number of tests that tie into a predefined test class and provide a high percentage of code coverage. If all tests pass with the required coverage, you can move it into production.
When salesforce issue new upgrades, they run all tests (for all custom code any user had added) against their upgrade beta. Ay test failures and they either fix their code or advise the developer that there is a problem.
It's a good concept - perhaps one to apply to "premier developer" program?
Cheers
Ian
By Ian Sampson on
4/28/2010 11:27 AM
|