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

HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForm and ListForm and ListWrong time for created or changed at... Wrong time for created or changed at...
Previous
 
Next
New Post
2/27/2007 2:42 PM
 

Jahall,

please accept, that DotNetNuke consists of several teams, spread all over the world - e.g. in this particular situation, there have been two of them involved (UDT and Q&A), which makes it more difficult to get things done "behind the scenes". This is the reason, why we need formalized processes.


Cheers from Germany,
Sebastian Leupold

dnnWerk - The DotNetNuke Experts   German Spoken DotNetNuke User Group

Speed up your DNN Websites with TurboDNN
 
New Post
2/27/2007 3:03 PM
 
See…this is a good example. You think I am arguing that there should NOT be formal processes, but that could not be farther from the truth. If you and I had been corresponding via phone, for example, it is unlikely that you would have drawn that conclusion. I am a big believer in process, in fact I commonly quote a saying “The system don’t work if you don’t work the system”, but ultimately the system does not replace common sense and direct communication.
 
Back to the issue…I was simply pointing out that if the person who originally marked my bug (log) report as withdrawn had contacted either you or me directly, before marking it as such, then any miscommunication would have been avoided.
 
Allen
 
New Post
2/27/2007 3:21 PM
 

Allen,

I read your issue and looked at the code for created at/ changed at to fix it today. For me this kind of issue is a showstopper which needs to be handled immediately. To my own surprise I found it already fixed – I had fixed the general handling of all date time data types some months ago, but did not remember myself. I looked up the history of this change; found the correct date and Gemini issue. Even if the fix is quite old, it is not yet part of any public release.

Now all for me to do was to spread the good news – adding a comment to your Gemini issue and answering to this thread. 

Afterwards your issue was closed by the QA team. This was not lucky, it should have been moved to the UDT project instead. Then I or Sebastian would have marked it as duplicate and it would have been closed though.

 
New Post
2/27/2007 4:29 PM
 
Once again, this is why processes don’t work if there is not DIRECT communication with all involved parties before decisions are made, in this case marking a case as Withdrawn.
 
Based on the information I could piece together between Sebastian and the support site, this is what I thought had happened:
 
1)      I posted in the UDT forum an issue known by the UDT team, but not formally documented. Otherwise why would Sebastian ask me to formally document it?
2)      Despite the fact that I thought it was odd that the project lead would ask me to document a known problem, I obliged and submitted one anyway.
3)      Within a couple of hours my support log was withdrawn by someone other than me, because the issue had supposedly been fixed in October.
4)      With no other info communicated I was left to make the following assumptions (and you know what those do )
a.       This problem was known, but not really fixed in Oct. since my brand new download and install of 4.4.1 still exhibited the problem.
b.      Individuals responsible for the fix had not completed it but advised Sebastian they had.
c.       The issue was going to be ignored.
d.      It was unlikely (since the issue was being ignored) that it would get fixed before the next release of DNN
e.       My effort to submit the case was a complete waste of time.
 
New Post
2/27/2007 4:33 PM
 
Also Stefan, If this issue was considered a showstopper then why has an update still not been released even though it was fixed in October?
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsForm and ListForm and ListWrong time for created or changed at... Wrong time for created or changed at...


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