Boost logo

Boost :

Subject: Re: [boost] boost trac for upcoming libraries?
From: David Abrahams (dave_at_[hidden])
Date: 2009-06-04 19:16:53

on Wed May 20 2009, Barend Gehrels <> wrote:

>>>>>> Is the Boost Trac system intended for official libraries only, or can we also
> use it for (to be) proposed libraries?
>>>>> Seems OK to me to use it for proposed libraries, as long as the use
>>>>> wouldn't cause confusion between proposed and accepted libraries.
>>>> I suspect confusion is very likely -- in particular, having bug report
>>>> against proposed library with target milestone of 1.40 would be fairly
>>>> confusing. Or, maybe there's some technical measure to limit possible
>>>> values of properties for bug reports?
>>> How about just name the component clearly, i.e. "[prop] FooBar" and then
>>> remove the tag once accepted. (And choose a good prefix scheme that make
>>> the proposed libraries end up last in the list.)
>> I think it would be *very* useful - but someone needs to work out the
>> details.
>> An extra target milestone might be 'Review'?
> Thanks for all answers. I think this will work and be useful for many libraries.
> However, our library (GGL) is quite large (also compared to other libraries), has
> several sub-components and, preparing for the review, will have an own
> library-specific roadmap and milestones (indeed one of them will be review). We will
> use those internally, and for the users we already have, for bugs, tasks and wishes.
> We now realize that it, at this moment, is not convenient to fit all these into the
> Boost trac.

Yeah, I've been wondering if might be a more appropriate
bugtracking system for us, or for example if we can do better with a
hybrid Trac system like OForge.

Dave Abrahams
BoostPro Computing

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