Boost logo

Boost :

From: David Abrahams (dave_at_[hidden])
Date: 2007-11-08 13:45:20

on Thu Nov 08 2007, Rene Rivera <> wrote:

> John Maddock wrote:
>> Rene Rivera wrote:
>>> Guillaume Melquiond wrote:
>>>> I have not followed the discussion closely, so I am probably missing
>>>> something, but why a new milestone? Unless I'm mistaken, issues that
>>>> are "fixed", "closed", and with a "1.35" milestone, are precisely
>>>> issues that will be fixed in the release (unless the relevant
>>>> patches are reverted). So I don't understand the need for a new
>>>> milestone.
>>> For exactly the "unless the relevant patches are reverted" situation.
>> Right: currently when something assigned to me was targeted for 1.35 I
>> closed it once it was fixed in the Trunk: otherwise there's no way to tell
>> what's been dealt with already :-)
>> So I would actually be in favour of either a "pending merge to release"
>> state, or else a new milestone for "1.35 Release Branch".
> After a bit of thinking... I thought it would optimally be good to have
> a ticket status to correspond to this. But it's not possible to change
> those in Trac.

Doug, can OSL please upgrade to Trac-0.11dev so we can have the ticket
workflow feature? Thanks.

> But there is one aspect we can use to describe the state, we can add
> a "Boost Release Branch" version, on par with the "Boost Development
> Trunk" version we have. So a ticket that is part of the 1.35.0
> milestone can:
> * Be tagged as version "Boost Development Trunk" if it's only in the
> trunk, whether it's resolved or not.
> * Be tagged as version "Boost Release Branch" if it's been merged
> successfully to branches/release. But only if it's resolved in the trunk
> and verified to resolved in the release branch.
> I think that follows the new release procedures accurately.

Well, the version field is traditionally for describing the version of
the software in which the issue is being reported.

Dave Abrahams
Boost Consulting

Boost list run by bdawes at, gregod at, cpdaniel at, john at