Re: [boost] when can a trac ticket be considered closed

Subject: Re: [boost] when can a trac ticket be considered closed
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2014-05-04 11:37:36

> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Klaim - Joël
> Lamotte
> Sent: 04 May 2014 16:11
> To: Boost Developers List
> Subject: Re: [boost] when can a trac ticket be considered closed
> 
> On Sun, May 4, 2014 at 5:02 PM, Marshall Clow <mclow.lists_at_[hidden]> wrote:
> 
> > Like so many things in Boost, this is up to the individual library
> > developers.
> >
> > In general, what _I_ do is:
> > 1) update the ticket when a fix is committed to develop.
> > 2) Close the ticket when the fix is merged to master.
> >
> 
> Would a ticket state that would mean "done/fixed in repo but not released yet"
help
> clarify things for both maintainers and users?

Well, as a maintainer, I may think that I've fixed and tested, but I'd like
confirmation from user(s) that *they* agree it is fixed for them too.

'Pushed to develop' tells users that if they want a 'hot fix', then go to
modular-boost/develop and pick it up.

'Pushed to master' tells users that this is a fix that will be in the next
release.

So I'd favour a ticket state for both of these, or at least some convention
about what 'fixed' means.

My two-pennyworth.

Paul

---
Paul A. Bristow
Prizet Farmhouse
Kendal UK LA8 8AB
[phone]