Subject: Re: [boost] [Master project] Switch from Trac to another Bug-tracking-system (was: [Master project] GitHub issues disabled)
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2015-04-24 05:05:29
> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Louis Dionne
> Sent: 23 April 2015 17:19
> To: boost_at_[hidden]
> Subject: Re: [boost] [Master project] Switch from Trac to another Bug-tracking-system (was:
> project] GitHub issues disabled)
> Deniz Bahadir <dbahadir <at> benocs.com> writes:
> > >>
> > >> The title pretty much says it all. Is there a reason for disabling
> > >> GitHub issues on the master project?
> > >
> > > Because we're still using Trac for bug reporting.
> > >
> > I would pretty much recommend, you consider migrating from Trac to
> > another (more modern) bug-tracking system that is more responsive and
> > has less problems with modern browsers.
> > [...]
> If the community wants to make a change, I think GitHub issues would be the most appropriate
> this, for obvious reasons since the repos are now hosted on GitHub.
> However, there are probably several valid reasons to stay with Trac too, so let's just say I'm
> naive wish.
Don't forget that many (good?) libraries use release notes and history that link to Trac #numbers to
record bugs and fixes and enhancements.
Any new system must continue to provide access the information that these provide.
This might be achieved by keeping Trac going (forever?) Conversion sounds non-trivial?
Any new system also needs to provide an equivalent mechanism to link to bug fix info.
--- Paul A. Bristow Prizet Farmhouse Kendal UK LA8 8AB +44 (0) 1539 561830
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk