Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...6.0.0 upgrade from 5.36.0.0 upgrade from 5.3
Previous
 
Next
New Post
7/22/2011 3:30 AM
 
Keivan

If you found the error before release it had been nice if you had logged it in gemini before release too.

I spend some time to locate the issue and logged it gemini issue 17304.
Then I had could used that time to locate a issue with the language parameter to get a installation to work.

So PLEASE log all known issues in gemini when you fiind them DNNCorp.
 
New Post
8/23/2011 1:06 AM
 
Jan Olsmar wrote:
So PLEASE log all known issues in gemini when you fiind them DNNCorp.

Jan:  

This really isn't a constructive statement and isn't a fair thing to say to Keivan.  I can tell you that we log every single bug and issue that we are aware of - regardless to whether you ever see it or find it.  

Keivan logged the issue less than 24 hours after it being discovered.  It is unrealistic to expect an issue that's discovered by anyone - DNN Corp or otherwise - to be logged the very second it is discovered.  In the case of DNN Corp, it is common to also take extra steps to further analyze the bug found.  The analysis can include any number of steps, impact analysis, and other processes/tests, which could very well cover a larger time span than you might consider to be appropriate.  However, the fact remains that a well-written and well-researched gemini report is better than simply copying and pasting an error.  In every single case, such a report would be more likely to have an impact and make it into the product as a fixed bug.  I hope you can appreciate the extra steps we take on a regular basis to ensure quality.


Will Strohl

Upendo Ventures Upendo Ventures
DNN experts since 2003
Official provider of the Hotcakes Commerce Cloud and SLA support
 
New Post
8/23/2011 5:37 AM
 
Will do you think your post is constructive?

Facts: I logged the issue before Kevin was logging the issue after spending quite a long time to find the cause of the issue. If you think my report is bad written its up to you but I think it has more information than Kevins, that is ok too.

Kevin tells that he found the issue before the release of DNN6. I found the issue after testing the release. I had the time to logg the issue. Kevin had not the time to logg the issue.

I had the time to check if the issue was logged before. Kevin had not the time to check if the issue was logged before. (By the way my initial issue is still not taken care of and marked as duplicate)

Will we can discuss quality and what is important. But not logging this known issue before the release was not quality. As a decition was taken to release the product with the known issue a note/blog/forumpost or whatever had been more quality.
 
New Post
9/7/2011 7:44 PM
 
I too do not have duplicates, but my skin is being listed as Legacy - would that be the issue?
 
Previous
 
Next
HomeHomeDevelopment and...Development and...Open Core Testi...Open Core Testi...6.0.0 upgrade from 5.36.0.0 upgrade from 5.3


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out