Subject: Re: [boost] [Master project] Switch from Trac to another Bug-tracking-system
From: Paul A. Bristow (pbristow_at_[hidden])
Date: 2015-04-25 05:18:06
> -----Original Message-----
> From: Boost [mailto:boost-bounces_at_[hidden]] On Behalf Of Deniz Bahadir
> Sent: 24 April 2015 10:47
> To: boost_at_[hidden]
> Subject: Re: [boost] [Master project] Switch from Trac to another Bug-tracking-system
> >>>> 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.
> > 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.
> As long as the release-notes only mention the issue #numbers, it should be enough to make sure,
> new ticket-system assigns the same ticket-numbers to the converted tickets. Probably, this should
> possible (as long as the new ticket-system supports migration from Trac, which is a prerequisite
> For Redmine I found a wiki-article about migration from Trac to Redmine, which states that ticket
> stay the same (if the Redmine-database is empty prior to migration). 
> For the case that some release-notes have direct web-links to Trac, not only issue-numbers, the
> "svn.boost.org/trac/" should still be available and automatically forward the browser to the
> address of the new ticket-system. For example (if using Redmine as new
> https://svn.boost.org/trac/boost/ticket/11224 --->
Some libraries do use the direct web-link to Trac item - it is by far the most convenient for users,
so this should continue to work.
> To be honest, I have not used too many different ticket-systems myself.
> However, as you might have noticed, I have some experience in working
> with Redmine and my impression is, that it would be a big improvement to
> using Trac and that a migration and database conversion from Trac to
> Redmine would be possible.
This is reassuring - but others have recommended using GIT issues (but without considering any
Are you offering to do the migration to Redmine?
(Personally, I have had no problems with Trac - just works for me).
Other views from experienced/disgruntled users?
--- 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