Subject: [boost] Trac tickets: fixed in trunk vs. fixed in release
From: Steve M. Robbins (steve_at_[hidden])
Date: 2009-02-21 12:35:43
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.
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?
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?
Boost list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk