[dist-bugs] Use cases, etc
Pierre Habouzit
pierre.habouzit at m4x.org
Wed Jul 9 09:59:51 EDT 2008
On Wed, Jul 09, 2008 at 12:20:55PM +0000, Lars Wirzenius wrote:
> Then, a couple of use cases or scenarios (not sure about the
> conventional terminology).
>
> * Report a new bug, either against the Debian package, or the
> upstream package, and have the information be shared to the
> other.
>
> * Ask for additional information related to a bug.
>
> * Add a comment to a bug, with more information to help the
> developer find and fix the cause.
>
> * Mark a bug as fixed, and include the fix or reference to it.
>
> So, the question is, how would Amanda, Brenda, and Cecil act in these
> cases? What would they do, how would the distributed system act, what
> data needs to go where, and how is stuff communicated between instances
> of the distributed tracker ("branches" in dvcs)?
They could all work with debbugs and let people that need all the power
of a DBTS import those bugs into their instance themselves. Users are
used to a central place with a GUI to look at bugs, this shall still
exist. Like you can have a gitweb on ~torvalds/linux-2.6.git where
people not wanted to perform a full clone can have a look.
One can dream that eventually debbugs becomes a DBTS by itself, hence
makes the communication with DBTS easier. But being a DBTS is not really
a feature that is exposed to users afaict, rather to "QA" people, or
people supposed to fix and triage bugs.
IMHO unlike a DVCS, a bug as a branch shall be some kind of unique
identifier, on which people may chose to have private modifications,
that they sometimes decide to share with others. If they want to deal
with a bug really differently, then they have to "clone" it, which would
in turn generate a new UUID (aka branch).
The rest probably should work like any bug tracker out there.
--
·O· Pierre Habouzit
··O madcoder at debian.org
OOO http://www.madism.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://kitenet.net/pipermail/dist-bugs/attachments/20080709/0358c5d3/attachment.pgp>
More information about the dist-bugs
mailing list