On Tuesday 14 November 2017 10:56:58 Michiel Beijen wrote: > Hi Pali, > > On Mon, Nov 13, 2017 at 6:18 PM, <p...@cpan.org> wrote: > > And I would suggest to disable issue tracker on github as primary bug > > tracker (according to DBD::mysql documentation) is on RT and also > > probably all problems are reported there. The worst thing which can be > > is to have two independent bug trackers, which is current situation. > > You're right, it would be helpful and desirable to have only one bug tracker! > > I've tried to migrate the existing RT tickets to Github before, but > that did not work correctly because DBD::mysql uses a Github > organization and the script I used at the time did not accept this. > I'll put it higher on my to-do list again and look into getting that > done.
Hi! As there are only few tickets on github, it would be easier to disable creating new tickets on github and those few which are not resolved yet either move on RT or (if github allows it; which I believe yet) continue to exists. And once any migration is ready, then it can be fully switched. Still one bugtracker is better then two, even if it is not on github.
