[darcs-users] An idea of a bug reporting system

'Andrew Pimlott' andrew at pimlott.net
Fri Aug 13 01:50:44 UTC 2004


On Fri, Aug 13, 2004 at 10:42:09AM +1000, BARBOUR Timothy wrote:
> > From: Andrew Pimlott [mailto:andrew at pimlott.net]
> >
> > Bug reports are always filed after the bug is checked in,
> > and there's no way (especially in a distributed system) to go back and
> > attach the bug to the patch that caused it.
> 
> If maintaining several branches (e.g. development and release), one could
> pull bug reports into the branch that the bug occurs in.

This still doesn't help anyone who pulls from eg a tag on the branch
that is after the bug and before the bug report.

Another issue with branches:  Say you have branches A and B, and you
find a bug that was introduced before they branched.  How do you get the
bug into both branches?  You don't want the people working on the
different branches to have separate discussions about the same bug.

> If darcs trackdown can locate the patch that introduced the bug, then one
> could make the bug report depend on it

But that doesn't help the bug report stay "with" the patch.  Ie, someone
can pull the patch and not get the bug report.

> [...]
> > The bug database should be "outside of time"
> > with respect to the code [...]
> 
> As I understand it, unlike any other revision control system, darcs is (by
> design) outside time.

Right, I'm not sure how to say what I meant.  Let's put it this way:
The bug database is a body of annotations to code patches.  You don't
really want to branch the annotations when you branch the code.  No
matter what set of patches you have in your repository, you want to see
all available annotations.

Andrew




More information about the darcs-users mailing list