Hi,
Am 27.09.19 um 13:33 schrieb Geert Janssens:
> Here's what I use as personal guidelines:
>
> * If I was able to reproduce the bug before applying the fix and I no longer
> can after the fix, I mark the issue as resolved. I typically add a message
> that the reporter can reopen the bug if the i
Here's what I use as personal guidelines:
* If I was able to reproduce the bug before applying the fix and I no longer
can after the fix, I mark the issue as resolved. I typically add a message
that the reporter can reopen the bug if the issue still persists, asking for
more details in that cas
Hi,
What is the correct way to mark bugs fixed.
Should I be marking them as RESOLVED/FIXED if I think I have fixed the
reported bug with appropriate text asking for the reporter to test and
reopen if not fixed.
or
leave it as NEEDINFO with some text asking for the reporter to test and
update the b
Am Mittwoch, 29. April 2009 15:29 schrieb Derek Atkins:
> Phil Longstaff writes:
> > There are 114 bugs which are marked as RESOLVED, FIXED with no target
> > milestone. I looked at a few of them, and they have a comment stating
> > that a fix was committed to trunk. They also had no comment sta
Phil Longstaff writes:
> There are 114 bugs which are marked as RESOLVED, FIXED with no target
> milestone. I looked at a few of them, and they have a comment stating that a
> fix was committed to trunk. They also had no comment stating that the fix
> had
> been back-ported. I'll be prepar
There are 114 bugs which are marked as RESOLVED, FIXED with no target
milestone. I looked at a few of them, and they have a comment stating that a
fix was committed to trunk. They also had no comment stating that the fix had
been back-ported. I'll be preparing the 2.3.0 release notes, so my q
