Slashdot Mirror

← Back to Stories (view on slashdot.org)

Bug Tracking Across Multiple Code Streams?

Posted by Cliff on from the one-bug-many-branches dept.

Eric Lennon Bowman writes "I've been using Bugzilla for a few years, and it has one particular shortcoming that is motivating me to look for alternatives. We very often find that a bug or feature requires changes to be integrated into several code branches, and there just isn't an elegant way (that I can see) to get Bugzilla to do that, short of creating a bunch of bugs, and linking them together as dependents (which is a bit inelegant, and error prone). I'd love the opinions of the Slashdot community on ways to deal with this problem, since it seems pretty widespread: How do you track the same bug across multiple versions of a product?"

4 of 33 comments (clear)

  1. Obvious advice means karma! by NanoGator · · Score: 1, Funny

    "How do you track the same bug across multiple versions of a product?"

    Fix it as soon as it's reported!!!

    --
    "Derp de derp."
  2. Quite simple, really by The+Iconoclast · · Score: 1, Funny

    I merely make sure there are no bugs in my code to begin with. :P

    --
    Quando Omni Flunkus Moritati
  3. Re:Fogbugz Solves This by TheMysteriousFuture · · Score: 1, Funny

    Wow...Can you say astroturfer?

    --
    .sig
  4. Too many forks... by Anonymous Coward · · Score: 1, Funny

    ...makes spoon jealous.