Boost logo

Boost :

Subject: Re: [boost] Trac tickets: fixed in trunk vs. fixed in release
From: vicente.botet (vicente.botet_at_[hidden])
Date: 2009-02-22 12:00:59


----- Original Message -----
From: "Vladimir Prus" <vladimir_at_[hidden]>
To: <boost_at_[hidden]>
Sent: Sunday, February 22, 2009 5:44 PM
Subject: Re: [boost] Trac tickets: fixed in trunk vs. fixed in release

>
> vicente.botet wrote:
>
>>
>> ----- Original Message -----
>> From: "Vladimir Prus" <vladimir_at_[hidden]>
>> To: <boost_at_[hidden]>
>> Sent: Sunday, February 22, 2009 4:18 PM
>> Subject: Re: [boost] Trac tickets: fixed in trunk vs. fixed in release
>>
>>> vicente.botet wrote:
>>>
>>>> Currently there are the following states: new, assigned, closed, reopened. We could add
>>>> * fixed_in_trunc: set when code commited in trunk branch with comment fixes #xxx
>>>> * verified_in_trunc: set when the associated test pass on trunk regression tests
>>>> * fixed_in_release: set when code commited in release branch with comment fixes #xxx
>>>> * verified_in_release: set when the associated test pass on release regression tests
>>>
>>> FWIW, we have good experience with "fixed, not delivered" and "fixed, delivered" states.
>>> I don't see the need for 'verified' states -- if somebody is not sure that a commit
>>> is actually fixing a bug, then he should mark the ticket as fixed only when necessary
>>> testing completes.
>>
>> It found making the difference necessary after the comment From: "David Abrahams"
>>>> 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.
>>
>> If this is automatic we need a manual state for the verified fix.
>
> Nobody forces you to add "Fixes #xxx" text in commit message if you're not
> sure the commit fixes anything. You can always add this string at a later
> time, if so desired.

Do you agree to have two status for fixed on trunk and fixed on release?
Vicente


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk