Archive
Monthly
Go
|
|
DNN Blog
Sep
17
Posted by:
Alex Shirley
9/17/2007 1:44 PM
Hi
My name is Alex Shirley (aka NukeAlexS) and if you've logged any issues this year in our bug tracker software Gemini, then the chances that I would have been your first point of contact. Right now you are my first point of contact because this is my first blog on this site. Anyway, it's my primary job when you log your issue in Gemini to validate it, decide where best it should be directed at, and how important it is. Once it reaches the core team they re-review what I did (often I get it wrong), and then they attempt the real work of getting the issue resolved.
Back in 2006 I looked at DNN and I felt that whilst it was a great application and fit for purpose (otherwise I wouldn't be using it), there were a large number of outstanding issues that I perceived were not being looked at. I just could not understand why really obvious issues were not being dealt with at all. In the end I posted a strong complaint in the forums, and rather the receive a message of complete indifference, or somebody telling me to stop whinging, I was asked by Shawn Mehaffie to join the QA team and help sort the problem out. I was rather taken aback to be honest, flattered, and in the end I just had to accept.
Moving on... it has been mine and the QA teams priority clean up the outstanding issues in the Gemini core and public projects, so the rest of the core team can do it's job efficiently, it has been a tall order, and right now I think we have a reasonable (but not perfect) picture of what is going on, so it's time to report in.
So it's my pleasure to publish some Dotnetnuke outstanding issue stats for the 4.6.0 release, and I hope this plays a part in making our open source framework more transparent to all of the DNN community. Of course these stats are always available on http://support.dotnetnuke.com, it's just that it's been very much hidden. I will be showing you how to monitor the situation yourself in realtime in a future blog entry, but right now here it is for your consumption:
Outstanding issues in DNN Core Framework 4.6.0 (at launch)
| |
Show Stopper
|
Major
|
Minor
|
Trivial
|
Total
|
PDF Report 
|
Bugs 
|
1
|
73
|
104
|
34
|
212
|
|
Tasks 
|
0
|
8
|
34
|
26
|
68
|
|
Enhancements 
|
1
|
100
|
261
|
199
|
561
|
|
New Features 
|
0
|
21
|
55
|
27
|
103
|
|
|
Total
|
2
|
202
|
454
|
286
|
944
|
|
Note that in order to give you a more realistic picture, issues set as require more info are not included in the above statistics. There are 24 require more info issues at present. Also note this is just statistics for the core framework application, sub-project stats are not included .
The PDF report contains detail on the actual issues involved.
As always we aim to get the number of issues down over the course of the next few releases, especially the bugs. Remember though that more often then not, as soon as one issue is fixed then another one is logged - the project never remains static! So if you are an ASP.NET developer perhaps you can help us by submitting code that will help put to bed our outstanding issues (more about how to do this will be in a future blog, but in a nutshell all you need to do is search for an issue in gemini and leave a comment that includes your code).
Please also realise that these are just figures, and in reality we don't actually know the full picture until the issue is resolved. So if you really want to get an idea of just how stable Dotnetnuke is, use it! Remember this is a heavyweight open source framework application, designed to be flexible, that is used by a heck of a lot of people around the world.
Finally I'd like to sign off by saying that 4.6.0 is just one heck of a release, I know people have worked really hard on this one, and our main body of core team members have been extremely active. They all deserve our thanks, and for me it's the best release yet.. so thanks team!
9 comment(s) so far...
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
Alex, thanks so much for stepping up to the plate and helping provide visibility to issues that need fixing. I did a talk at the Philly Code Camp this past weekend, called DNN Alive and Well. The new functionality in DNN 4.60 and the focus on fixing existing bugs certainly helps provide confidence that DNN is not a passing fad and is a good choice for a Web Application Framework.
By jbonnie on
9/17/2007 2:26 PM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
Great material Alex!
By hooligannes on
9/18/2007 9:01 AM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
An Idea...Give people that know how to fix code an incentive to debug, fix, and document the fix by giving their issue a high priority. Create a new category for issues that have source code included to fix the issue. Put it next to Show Stoppers and give it a high priority even if it is for a minor issue.
By jlehew on
9/21/2007 1:15 AM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
[NOTE YOUR COMMENT APPEARS TO HAVE BEEN LOST APOLS JLEHEW, HERE IS THE RESPONSE ANYWAY] Yes this is something I have been pondering about over the last week . This enhancement will turn gemini into a knowledge base as well as a bug tracking forum. I can see arguements for and against this with the resources we have available, and we might also need more meaty software to do this particular part of the job effectively (i.e. do it wiki style, unfortunately gemini doesn't not contain functionality like this right now). It's something to consider for sure, but for now it's the DNN community who provide this wealth of knowledge in the forums.
By NukeAlexS on
9/22/2007 2:06 AM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
944 issues in 1 release is quite an achievement. So you're doing a great job Alex....
By trouble2 on
9/22/2007 2:04 AM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
@ jlehew - We introduced the "code for review" staus just a few weeks ago. This week I went through all our outstanding issues and marked the relevant ones, this now stands at 90 issues outstanding. So I completely agree with your comments here.
By NukeAlexS on
9/22/2007 1:54 AM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
@trouble2 - I don't really fix the issues trouble2, I just make them more prominent and validate them. The core team does the real work. So it's very much a team effort. These 944 issues are issues outstanding not issues dealt with, I wish there were 944 issues dealt with, then we all could go home job done :) Note there were a heck of a lot of issues fixed 4.6.0 which can be found here: http://support.dotnetnuke.com/project/ChangeLog.aspx?PROJID=2 Thanks for your comments!
By NukeAlexS on
9/22/2007 2:01 AM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
So why is there a 4.6.0 with all these fixes? Shouldn't it have been a 4.5.6 release? I thought the major point releases were going to be for new major features. I almost have to upgrade to kill the bugs, but I also don't want to implement new features that haven't been through the ringer yet.
By ech01 on
10/3/2007 8:25 PM
|
Re: DotNetNuke outstanding issue stats for the 4.6.0 release
@ech01 - 4.6.0 killed a load of bugs, and introduced a few as well. This has been stabilized since 4.6.2 (we went through quite a rough ride), although (as always) there are still outstanding issues. There were also new features introduced in 4.6.0. In my view every new release should kill bugs (the more bugs crushed the merrier in my opinion). As to how a release should be labelled, and when new features should and shouldn't be released, well I'll leave that discussion to the forums if you don't mind :).
By NukeAlexS on
10/3/2007 8:36 PM
|
|