Guten Tag Jonathan Oulds, am Donnerstag, 13. Januar 2011 um 17:46 schrieben Sie:
> Currently we track bug fixes by including a reference number within the > commit message, I'm sure this is common practice. If you already use a bug tracker, doesn't that provide a mechanism to file bugs against multiple versions or maybe clone bugs into multiple versions? Bugzilla for example does the latter, at least in my old 2.22.x, which wouldn't directly answer the question which bug does span over multiple versions. But what you could do is create some master bug for your error and dependant bugs for each version in which this error occurs. At least you could use the reporting tools of your bug tracker. In my opinion, depending on the concrete bug and how important it has to be fixed and all that stuff, having more than one bug for the different versions is of benefit if you think of things like branches which aren't supported anymore and therefore don't need a bug fix, some need a fix but not now, for some branches this bug is a show stopper etc. I would use the bug tracker for such things. Mit freundlichen Grüßen, Thorsten Schöning -- Thorsten Schöning AM-SoFT IT-Systeme - Hameln | Potsdam | Leipzig Telefon: Potsdam: 0331-743881-0 E-Mail: tschoen...@am-soft.de Web: http://www.am-soft.de AM-SoFT GmbH IT-Systeme, Konsumhof 1-5, 14482 Potsdam Amtsgericht Potsdam HRB 21278 P, Geschäftsführer: Andreas Muchow
