Forgot your password?
typodupeerror

Comment We're trying to develop such an open source tool (Score 1) 174

We're currently working on trying to develop such an opensource tool that would allow bugs synchronisation between different bugtrackers. There's not much yet as the project just started a couple weeks ago, but I hope we can achieve something to solve that issue. Our first tasks have been to look at bts-link and also investigate the use of ontologies, RDF and semantic annotations or Linked Data concepts. More details here : https://picoforge.int-evry.fr/cgi-bin/twiki/view/Helios_wp3/Web/

Comment Re:Debbugs (Score 1) 174

* Keep track of bugs forwarded upstream and automatically update the bug status at home (to fixed-upstream) when the upstream bug is fixed.

Well, actually, it's not exactly debbugs which handles that, but bts-link which explores remote bugs in distant (upstream) bugtrackers and notifies accordingly.

Bug

Submission + - How to track the bug-trackers?

schneecrash writes: Submitting bug reports — and waiting for responses etc — seems to be SOP for developers and users alike, these days.

Every project has some sort of bug-tracker — bugzilla, trac, mailing list, etc etc.

E.g., we currently track 200+ external bugs across ~40 OSS projects. Half the bugs depend on something else getting fixed, first. Every bug has its own email thread, etc. Management asks "How we doin' overall?", and suddenly everyone involved gets to work removing dried gum from the bottom of their shoe ...

What do /.-ers use/recommend for centrally keeping track of all the bugs you track across all those different bugtrackers? In particular, managing communications and dependencies across bugs?

So far, the best method I've managed to use is bunches of PostIt-notes stuck to the screen of an out-of-commission 32" TV (glossy, non-matte screen, of course!).

Slashdot Top Deals

"Mr. Spock succumbs to a powerful mating urge and nearly kills Captain Kirk." -- TV Guide, describing the Star Trek episode _Amok_Time_

Working...