Subject: Re: [boost] [trac] Boost v1.64 in the milestones?
From: Stefan Seefeld (stefan_at_[hidden])
Date: 2016-12-17 14:42:00
On 17.12.2016 14:22, Daniel James wrote:
> On 17 December 2016 at 17:51, Stefan Seefeld <stefan_at_[hidden]> wrote:
>> As I have said before, I'd really live it to the individual projects
>> what tools they use (Boost.Python has moved to its github tracker, and
>> no new issues on trac are allowed.)
> I generally agree with projects choosing their own tools, but from the user
> perspective, we really do need a single place for them to report bugs.
> Dealing with one bug reporting system is bad enough.
I partly agree, but again, this depends on lot on the project in
question. For example, Boost.Python bugs are typically very
self-contained, and Boost.Python users know the project and don't need
to be routed through some official Boost (meta-)tracker.
Other projects / modules may be less independent, so it might not always
be obvious for users where to report issues.
A toplevel page with some guidance would be very useful in any case, and
perhaps even a "catch all" tracker for users who don't know where else
to report the issue. (Though I figure that to be the exception rather
than the rule.)
-- ...ich hab' noch einen Koffer in Berlin...
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk