> Since opinions on that will vary, a bug tracking system that can be used
> either way seems likely to be more widely useful than a bug tracking
> system that restricts its use to only in a different git repository,
> or only in the same git repository as the code. Unless, of course,
> there's some other, technical reason to chose one or the other.

Other than conflicts of branch names, I don't see any strong reason why
a BTS in a Git repository would collide with other uses of
this repository.  Currently BuGit would conflict in the sense that it
uses "master", but I'll probably change that at some point so that all
the branches it uses are under the "bugit/" namespace, thus making it
possible to use the same repository.

The more serious problems come up when considering the choice of sharing
a *branch* rather than a repository (and I think most people who talk
about sharing a repository are really thinking of sharing a branch
rather than only sharing the repository).

This is a much more fundamental design choice with far reaching
consequences.  E.g. sharing the branch with the code implies that all
the data is stored in a single branch, so all the history of the various
issues is necessarily intertwined.  It also implies the notion of having
several concurrent branches of your issue database (potentially on the
same host) which are not meant to be merged (not yet, or not ever).

It also makes it more difficult to share an issue between two
databases (e.g. have an issue in Debian's database be kept in sync with
the corresponding issue in the upstream maintainer's issue database).
At least more difficult than a design like BuGit's where it takes little
more than a "git push/pull".

> So the question may be, what needs to change to get distributed bug
> tracking to extend beyond quick and easy systems built for essentially
> personal, or at best project-wide use?

Good question,


        Stefan
_______________________________________________
dist-bugs mailing list
[email protected]
http://kitenet.net/cgi-bin/mailman/listinfo/dist-bugs

Reply via email to