Archive
Monthly
Go
|
|
DNN Blog
Nov
7
Posted by:
Alex Shirley
11/7/2007 12:57 AM
Well it's a big times ahead for the DNN project, DotNetNuke 4.7.0 has just been released, and some major announcements have already been made at OpenForce in Las Vegas (news travels fast to a rainly London flat).
With all this going on it might be easy to think that the core team has had no time to improve the DNN platform. Well this is not true, if you in any doubt I have two words for you: Change Log.
Below I present some stats to help increase your information overload for today :):
Number of outstanding issues in DNN Core Framework 4.7.0 (at launch)
| |
Show Stopper
|
Major
|
Minor
|
Trivial
|
Total
|
Bugs 
|
0
|
42
|
82
|
28
|
152
|
Tasks 
|
0
|
26
|
81
|
87
|
194
|
Enhancements 
|
0
|
61
|
194
|
138
|
393
|
New Features 
|
0
|
25
|
62
|
38
|
125
|
|
Total
|
0
|
154
|
419
|
291
|
864
|
Total number of require more info issues that were not counted in these stats is 2.
Increase/decrease of outstanding issues between 4.6.0 and 4.7.0 (at 4.7.0 launch)
| |
Show Stopper
|
Major
|
Minor
|
Trivial
|
Total
|
Bugs
|
-1
|
-31
|
-22
|
-6
|
-60
|
Tasks
|
0
|
+18
|
+47
|
+61
|
+126
|
Enhancements
|
-1
|
-39
|
-67
|
-61
|
-168
|
New Features
|
0
|
+4
|
+7
|
+11
|
+22
|
|
Total
|
-2
|
-48
|
-35
|
+5
|
-80
|
Important points to note here:
1) There were a number of issues logged during the timeframe of the 4.6.0 and 4.7.0 releases. So these stats are never static. Withdrawn issues (e,g. because they are duplicate, or cannot be reproduced) are not counted in above stats.
2) Since 4.6.0, every issue has been re-reviewed and adjustments have been made. For this reason the number of tasks and new features went up significantly whilst the number of enhancements went down. Consequently I think we have far more accurate figures here, but note these are never entirely accurate (see point 3).
3) Issues are always re-reviewed on a constant basis. In many instances we only know the true nature of the issue after a fix has been identified.
4) The total number of require more info issues has gone down by 22 (which means that a lot of these issues are now counted in the stats).
5) To find out exactly what the issues outstanding are, please look at my last blog entry here on how to identify them.
6) For the real picture on what has been fixed in 4.6.1, 4.6.2 and 4.7.0, please consult the change log for further information.
Hope this helps!
Congratulations to the team for all their hard work and a great release. I only wish I was there at OpenForce. Next year maybe!
5 comment(s) so far...
Re: Progress with DotNetNuke 4.7.0
Great work, i would like to get roles with testing new release (at beta stage), however my application haven't accepted for this release.
By greenflash on
11/7/2007 5:48 PM
|
Re: Progress with DotNetNuke 4.7.0
I think, DNN 4.5.5 is the best, I don't use nearly version, because it many bug
By nminhkha on
11/7/2007 5:48 PM
|
Re: Progress with DotNetNuke 4.7.0
nminhkha, take a look at the chagelog and see for yourself the realton between bug fixes and enhancements. It is only that you might run into bugs you are not familar with. Every release is a big step in progress.
By cshark on
11/7/2007 11:31 PM
|
Re: Progress with DotNetNuke 4.7.0
I normally take about 4 weeks after release trying out the software. I don't immediately install (far from it). I also monitor gemini during that timeframe for any new bugs that I can't work around easily. In this way I can form an opinion as to whether I stick with what I have or upgrade. Also if there is anything drastically wrong that needs to be fixed it's more than likely a new release will come during that timeframe (but please don't hold me to this, in the end it's the core teams decision :).
By NukeAlexS on
11/7/2007 11:37 PM
|
Re: Progress with DotNetNuke 4.7.0
I have a very good experience with 4.6.0 (It is very stable).
Horacio Lampe
from Argentina
By hlampe on
12/4/2007 6:56 PM
|
|