On 4/27/12 7:34 AM, Igor Galić wrote:
----- Original Message -----
Hi all,
James suggested a while ago that we change how we deal with
backported bugs.
I agree with him that our system of closing, reopening, reassigning
etc. is
not only complicated, but difficult to follow.
His suggestion was simply to clone a bug that has been approved for
backport, and mark that for the backport version. Jira supports this
I'm
fairly certain. This would make the original bug kept closed after
committed to trunk, and the cloned bug is used exclusive for the
backport(s).
The one objection I've heard is that this could duplicate the number
of bugs
that we have, but the per release statistics would not change in any
way.
What do you guys think? I'm personally +1 on this idea.
Which bug number goes into CHANGES then?
The cloned one I'd imagine. It would have all the previous history (since
it's a clone), in addition to the commit message(s) for the backport.
I can see the potential "confusion" that trunk and a stable release has
different TS-xyz numbers for the same fix. But on the other hand, it's now
also clear that it's a backport bug, potentially with merge fixes etc.
-- Leif
