bug resolution states

Randy Kramer rhkramer at gmail.com
Sat Nov 15 17:20:36 GMT 2008

On Saturday 15 November 2008 06:40 am, Michael Leupold wrote:
on't think a bug like that should be RESOLVED without the recheck. We've 
> been already talking about a kind of flag to set like 
> In my opinion it could be used both for bugs needing more information 
to start 
> working as well as bugs needing a recheck.
> I think the workflow should be:
> 1) Bug you can't reproduce+
> 2) Some minor changes that might fix it
> 3) Set the NEEDSINFORMATION flag
> No information => close the bug as REMIND after an appropriate amount 
of time.

Not bad, but it's a shame that bugzilla (is that what we're talking 
about) seems so inflexible (hard to hack) that we can't pick a word or 
SHORTUNSPACEDPHRASE to more precisely describe the condition.

No, I don't have a suggestion (yet) on that word or phrase--well, ok, 
brainstorming some phrases:
   * ???

Without ever having fooled with bugzilla innards, my impression is that 
it's primarily a database application?

Randy Kramer
I didn't have time to write a short letter, so I created a video 
instead.--with apologies to Cicero, et.al.

More information about the kde-core-devel mailing list