| |||||||||||||
|
| |||||||||||||
Distributed bugsDistributed bugsPosted May 15, 2008 12:59 UTC (Thu) by emk (subscriber, #1128)In reply to: Distributed bugs by tialaramex Parent article: Distributed bug tracking
Hmm. This is an excellent and interesting idea. We frequently need to shift bug reports
between projects at work: "Oops! That's not our bug. That's really a bug in $OTHER_LIBRARY."
Working out the semantics may be challenging, though. In particular, the original project
needs to keep some sort of "tracking bug" (probably just the same bug), and remember where to
pull updates from.
You'd also want tags--not in a git sense, but in del.icio.us sense ("release-1.2",
"subsystem-foo", "mystery-crasher"). And those might need to be project- or
maintainer-specific under certain circumstances.
And would there be new "resolution" values? "Waiting for upstream to fix", for example?
(Log in to post comments)
Distributed bugs Posted May 17, 2008 18:47 UTC (Sat) by vonbrand (subscriber, #4458) [Link] The technical problems to be solved are (comparatively) trivial (even a single bugzilla keeping track of all bugs would be enough to solve half of it or so), the hairy, so far unsolved problems are the organizational (people) problems.
|
|
||||||||||||