Activity log for bug #332061

Date Who What changed Old value New value Message
2009-02-20 14:12:59 Martijn Faassen bug added bug
2009-02-20 14:13:36 Martijn Faassen grok: importance Undecided High
2009-02-20 14:13:36 Martijn Faassen grok: assignee d2m
2009-02-20 14:13:36 Martijn Faassen grok: statusexplanation
2009-02-20 14:13:36 Martijn Faassen grok: milestone 1.0
2009-02-24 22:29:24 Martijn Faassen grok: milestone 1.0 1.0a2
2009-03-04 18:42:47 Martijn Faassen grok: importance High Critical
2009-03-06 05:40:50 Michael Haubenwallner grok: assignee d2m uli-gnufix
2009-03-06 10:09:51 Uli Fouquet grok: status New In Progress
2009-03-06 10:09:51 Uli Fouquet grok: statusexplanation Thanks, Michael! Your hint with `zopeproject` was valuable.
2009-03-06 12:21:55 Uli Fouquet grok: status In Progress Fix Committed
2009-03-06 12:21:55 Uli Fouquet grok: statusexplanation Thanks, Michael! Your hint with `zopeproject` was valuable.
2009-03-06 16:22:33 Uli Fouquet grok: status Fix Committed Confirmed
2009-03-06 16:22:33 Uli Fouquet grok: statusexplanation Okay, I reopen the bug to have it invesitgated further. I am not sure about the rollback, however, because a more intelligent handling of requests in the index view might be okay. I'll update (rollback) the grokui.admin docs anyway. Beside this I think there is nothing wrong with the approach to let users slip through that call the index page with the WSGI debugger enabled. Let's call it a convenience feature. There is nothing to stop users from creating their own debug.ini if we do not deliver one with grokproject.
2009-06-25 11:02:55 Reinout van Rees tags europython2009
2009-07-07 11:00:51 Uli Fouquet grok: status Confirmed In Progress
2009-07-13 18:30:59 Uli Fouquet grok: status In Progress Fix Released
2009-07-13 18:32:31 Uli Fouquet grok: status Fix Released Fix Committed
2009-10-08 05:47:15 Michael Haubenwallner grok: status Fix Committed Fix Released