bug resolution states

Jordi Polo mumismo at gmail.com
Sat Nov 15 11:12:27 GMT 2008

What I ask is somewhat different.
I can not reproduce (as of REMIND)
but I did modify the code to something that makes more sense and possibly
close the bug.

For instance, a bug report says that something crash.
It is not crashing for you and the code is pretty trivial but take a look at
it and locate an ASSERT where you think should be only a return -1;  change
it and make more sense. Of course, the code is still not crashing.
In this kind of case  WORKSFORME is acceptable?

On Sat, Nov 15, 2008 at 4:36 AM, Michael Leupold <lemma at confuego.org> wrote:

> On Friday 14 November 2008 19:51:33 Randy Kramer wrote:
> > On Friday 14 November 2008 11:38 am, Matt Rogers wrote:
> > > On Friday 14 November 2008 06:17:36 Jordi Polo wrote:
> > > > I can not reproduce the bug but checking the code I solved an
> > obvious
> > > > problem that surely have solved the bug also but as I could not
> > reproduce
> > > > the bug I can not tell for sure either.
> > > > It is basically a call for the people that is bitten by the bug to
> > update
> > > > sources/packages and try again.
> > > Just use WORKSFORME instead.
> > As a non-developer, works for me implies (to me) (or I infer from
> > WORKSFORME) that the bug could not be confirmed and no work was done on
> > it.  It would not (unless there was something else there) hint that I
> > should try it out because something has been done.
> I usually use WORKSFORME to indicate that no work has been done and I'm
> pretty
> sure that there's no bug. I use REMIND for bugs that can't be reproduced
> due
> to lack of response. I usually leave a comment explaining that and ask to
> reopen if the reporter can provide more information (which is barely the
> case
> with bugs that have been waiting for more information for more than a
> month).
> Regards,
> Michael

Jordi Polo Carres
NLP laboratory - NAIST
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20081115/ddaa6bf1/attachment.htm>

More information about the kde-core-devel mailing list