[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Practical solutions to: the new style "mass tirage" of bugs

On Thu, Feb 21, 2008 at 11:31:32PM -0600, John Goerzen wrote:
> Here are some things that occur to me quickly:

I'll be just pointing to existing tools I'm aware of that are related to
your points. People probably already know all of them, but since I'm a
bit surprised to not having them mentioned in this thread I'll do that.

> 4) Integration with BTS and $DVCS.  I have some code that marks bugs pending 
> when mentioned in a VCS change log.  But this could go farther: branches 
> tied to bugs, etc.

My workflow for that is using dch + debcommit + tagpending, all in
devscripts. With dch I play with the changelog as usual, possibly adding
the "Closes: #xxxxxx" entry. Then I commit with debcommit, which reuses
the changelog entry as it is. Then I run tagpending which extracts bug
numbers from the changelog entry and send the appropriate message to the

I find this quite satisfying, the only extra integration which I would
like is alioth-side post-commit hooks (which I believe exists for
whatever $VCS) grepping for "Closes: #xxxxxx" lines in commit messages.
It won't be life changing, but having them by default on all repos on
alioth would be nice.

Were you expecting something like this? more/less?

> 6) Better tools to integrate Debian BTS with upstream BTS.  I would love a 

Uhm, we have bts-link (http://bts-link.alioth.debian.org/) which is
quite nice, though I must say that thus far I've been lucky, and
madcoder has always made the setup I needed instead of me :-)

> command-line tool where I could say "debforward 123456".  It would look up 
> the package name for 123456, figure out from some metadata what type of BTS 
> it uses and where it lives, look up my account on that BTS in ~/.forward, 
> and create a bug report there and mark the Debian one forwarded.  Then, if 
> there is no automated mechanism, some scanner at Debian would look for 
> changes on either end and forward them back and forth.  I would love this.

I guess madcoder already have this kind of information for bts-link, if
the information is available somewhere it would be trivial to add this
feature to bts (the commandline tool in devscripts, not the BTS of


Stefano Zacchiroli -*- PhD in Computer Science ............... now what?
zack@{upsilon.cc,cs.unibo.it,debian.org}  -<%>-  http://upsilon.cc/zack/
(15:56:48)  Zack: e la demo dema ?    /\    All one has to do is hit the
(15:57:15)  Bac: no, la demo scema    \/    right keys at the right time

Attachment: signature.asc
Description: Digital signature

Reply to: