I have marked this bug as fixed, because Alex has written some patches that, indeed, fix it. But these will be held back until after the code freeze, so the bug is still actually present in the current code. Would it be preferable to reopen it, therefore, until the patches are actually applied?
Thanks,
On Saturday May 10 2008 13:49:03 Andrew Talbot wrote:
I have marked this bug as fixed, because Alex has written some patches that, indeed, fix it. But these will be held back until after the code freeze, so the bug is still actually present in the current code. Would it be preferable to reopen it, therefore, until the patches are actually applied?
Bug should be marked as fixed *only* after a fix has been committed. So if it isn't committed yet it should stay open.
Andrew Talbot wrote:
I have marked this bug as fixed, because Alex has written some patches that, indeed, fix it. But these will be held back until after the code freeze, so the bug is still actually present in the current code. Would it be preferable to reopen it, therefore, until the patches are actually applied?
Thanks,
The bug should stay open and the fix patches be attached to the bug in case someone else wishes to incorporate them into a private build.
James McKenzie
-
Andrew Talbot -
James McKenzie -
L. Rahyen