Subject: Re: [boost] Trac tickets: fixed in trunk vs. fixed in release
From: David Abrahams (dave_at_[hidden])
Date: 2009-02-21 19:02:29
on Sat Feb 21 2009, "Steve M. Robbins" <steve-AT-sumost.ca> wrote:
> For each bug, there are really two levels of "fixed": roughly
> speaking, the developer considers the issue fixed when it is committed
> to trunk, while the user considers the issue fixed when it is
> commited to the release branch.
Yes, this is one place our current branching system is breaking down.
> At present, the trac ticket is closed at the first gate.
> Unfortunately, sometimes the second gate gets forgotten. Could
> another state be added to the ticket lifecycle to track when it gets
> merged to release?
It's an excellent idea. We should also update the post-commit hook to be able
to close the ticket when "fixes #xxx" shows up int the checkin comment
on the release branch.
> My aim is to be able to identified "fixed" tickets that are not
> actually released and, hopefully, to decrease them in number. Maybe
> there are other ways to achieve this?
I'm afraid there's no easy way. I usually just pore through the diffs
between trunk and branches/release.
-- Dave Abrahams BoostPro Computing http://www.boostpro.com
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk