Question/Proposal: "Maybe fixed" state
Posted: 04 January 2018, 11:15
Hi everybody,
I was wondering what state I should use for bugs that may have been fixed (in the bug list).
I explain: I corrected an important issue on my code that could be the cause of several noticed bugs. The problem is I can't easily reproduce a situation that used to be buggy and check that the bug is gone, but I'm confident that bug has been effectivly solved, but I can't bring the proof of that. Since I can't be 100% sure (even if there is no more vote for 5 days), I am reluctant using the "fixed" state. However, I would like not to let it open since I won't work on it anymore until new external information is brought.
Do you use another state to mark that ("worksforme"? "wontfix"?) ? If not, I would turn that discussion into a proposal for the BGA team to introduce that new state. If so, all regular players should be allowed to switch back the state of this bug on "open" or "confirm" if this bug is still encountered.
Any experience with that?
Thanks a lot,
Jean
I was wondering what state I should use for bugs that may have been fixed (in the bug list).
I explain: I corrected an important issue on my code that could be the cause of several noticed bugs. The problem is I can't easily reproduce a situation that used to be buggy and check that the bug is gone, but I'm confident that bug has been effectivly solved, but I can't bring the proof of that. Since I can't be 100% sure (even if there is no more vote for 5 days), I am reluctant using the "fixed" state. However, I would like not to let it open since I won't work on it anymore until new external information is brought.
Do you use another state to mark that ("worksforme"? "wontfix"?) ? If not, I would turn that discussion into a proposal for the BGA team to introduce that new state. If so, all regular players should be allowed to switch back the state of this bug on "open" or "confirm" if this bug is still encountered.
Any experience with that?
Thanks a lot,
Jean