On Wed, May 14, 2014 at 1:14 PM, Paul A. Bristow
-----Original Message----- From: Boost [mailto:boost-bounces@lists.boost.org] On Behalf Of Neil Groves Sent: 14 May 2014 09:43 To: boost@lists.boost.org Subject: [boost] Trac request states - suggestion
Dear Boost Developers,
While working with Trac to maintain Boost.Range I find that I frequently have solved issues but they are not ready to be merged to master due to the release schedule. I haven't noticed a way in Trac to denote that the issue is fixed and waiting to be merged. This means that I frequently look up tickets that I have forgotten I have fixed. It also means that I have a sub-optimal process for merging to master.
I wondered if we might be able to squeeze in a "fixed in branch" field. It would help me considerably. Do other developers think this would help?
Yes - I think states of
'fixed in develop' (awaiting possible user feedback?)
'fixed in master' branches (really believed fixed)
'fixed in release 1.xx' would be good. (fix has actually hit the streets)
(Of course not having to remember to update would be even better but ...)
I think most people won't remember that. I certainly won't. :) I'd say 'fixed in release N' is only useful if it is set automatically for all tickets in 'fixed in master' by the release procedure (script?). Not sure if it's doable.