Boost logo

Boost :

Subject: Re: [boost] Respecting a projects toolchain decisions
From: Steven Watanabe (watanabesj_at_[hidden])
Date: 2010-12-30 01:09:51


On 12/28/2010 3:34 AM, Vladimir Prus wrote:
> Dean Michael Berris wrote:
>> Imagine if you had one issue tracker per Boost library. Then you don't
>> have to worry about crafting the queries to get the relevant
>> information in the first place. And then it's going to be easier to
>> develop milestones per library than creating one big milestone and
>> having one giant release. You can then have different workflows per
>> Boost library depending on what the developers of the library are
>> comfortable with.
> I'd be very much against the idea of checking 4 different sites as
> opposed to 1 -- at least, until I have 4 pairs of hand to work on
> 4 different projects at the same time. In fact, I so much dislike
> having to check N different issue trackers that I have a student working
> on a tool to present issues from different trackers in a single UI. However,
> until that project is done, I'd much rather not having things split up
> unnecessary.

I very strongly agree. I periodically go through every open
ticket in trac. Having separate issue trackers would make this
practically impossible.

In Christ,
Steven Watanabe

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