Hi,
From: "Jonathan S. Shapiro" <shap@eros-os.org>
> A bug is not fixed when code is checked in. A bug is fixed when a test
case
> or test cases demonstrating the bug run correctly.
>
> You definitely *do not* want tracking of which bugs are fixed to be
> automatic. When you merge a good branch with something else, bugs may
> regress. The only way to know is to run tests.
Humm... to me this is a half-truss. While I agree that a bug is not "fixed"
when code is checked-in, the code check-in is part of the life of the bug:
it indicates that now this particular bug should be restested (actually you
could call the check-in a "fix" while the important event for a bug is
"close"). As such it makes sense to track both with the same tool: you
check-in some code becose of such and such PR, it would be nice to see these
PRs state updated accordingly (which does not mean that they are closed).
The goal here is to automate the process where it makes sense. However I
think that this is more like a secondary issue at this time. Maybe a version
2 item ?
Patrick.
Received on Sat Oct 21 14:36:05 2006