Boost logo

Boost :

Subject: Re: [boost] [1.45.0] release note are insufficient
From: Vladimir Prus (vladimir_at_[hidden])
Date: 2010-11-25 01:20:30


Marshall Clow wrote:

> On Nov 24, 2010, at 7:17 PM, Steve M. Robbins wrote:
>
>> Someone wrote:
>>>>> I want to know the complete list of changes.
>>
>> I agree; it would be a useful thing.
>>
>>
>> On Tue, Nov 23, 2010 at 08:33:58AM -0600, Matt Chambers wrote:
>>
>>> If the tracker is being used correctly, shouldn't the complete list
>>> of bug fixes be a query on the tracker for issues that were known in
>>> <version-1> and have been fixed in <version>?
>>
>> Bugs are marked "fixed" as soon as the change is made in the trunk.
>> However, the release procedure requires a second, manual step to merge
>> the fix into the release branch.
>>
>> One problem I've repeatedly run into is that the second step is often
>> missed. The result is that the issue tracker is much less useful than
>> it could be. I think that would have to change before your idea
>> (which otherwise appeals to me) would work.
>
> FWIW, what I do is that I add a note to the trac ticket when I fix the bug on the trunk, and then
> close the ticket when I merge to release.

Another alternative is to make release notes live in the same SVN tree as the code. Then,
one will add a release note when fixing bug, and a subsequent merge to release branch
will pick the release note as well. But the requires some tool support.

- Volodya


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