Subject: Re: [boost] [GIT] What happens to the Trac?
From: Dave Abrahams (dave_at_[hidden])
Date: 2012-12-17 15:38:51
on Mon Dec 17 2012, Julian Gonggrijp <j.gonggrijp-AT-gmail.com> wrote:
> Dave Abrahams wrote:
>> on Mon Dec 17 2012, Julian Gonggrijp wrote:
>>> All valid points, but what's wrong with keeping trac for the old
>>> issues while requesting (or perhaps just encouraging, initially) that
>>> people submit new issues to the GitHub tracker?
>> 1. We shouldn't make too many changes all at once
>> 2. Fragmentation
> Every GitHub repo includes an issue tracker by default (this appears
> to be true of all current Boost repos as well). Users who don't know
> better will submit their issues there. Are you going to switch off the
> trackers for all GitHub repos (this seems to be possible) in order to
> stop them?
> If not, how do you plan to prevent the change and fragmentation?
> In the latter case, my suggestion to request or encourage that new
> issues be submitted to GitHub might actually help to reduce
> fragmentation. But I wouldn't necessarily object against closing the
> GitHub trackers either.
Those can always be opened later, but initially they should be closed.
-- Dave Abrahams BoostPro Computing Software Development Training http://www.boostpro.com Clang/LLVM/EDG Compilers C++ Boost
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk