Re: Bugtracker DBD::mysql

2017-11-15 Thread Michiel Beijen
On Tue, Nov 14, 2017 at 5:40 PM, Dan Book wrote: > I also prefer github but of course it's mainly up to what is easiest for the > maintainers. Here is a script for migrating tickets if it's not what you > already tried: https://metacpan.org/pod/RTx::ToGitHub Actually, that is

Re: Bugtracker DBD::mysql

2017-11-15 Thread Patrick Galbraith
I agree on getting of RT to Github. Basically, it's 2017 and github is good at what it does. On 11/14/2017 11:40 AM, Dan Book wrote: On Tue, Nov 14, 2017 at 8:34 AM, Michiel Beijen > wrote: On Tue, Nov 14, 2017 at 11:07 AM, 

Re: Bugtracker DBD::mysql

2017-11-14 Thread Dan Book
On Tue, Nov 14, 2017 at 8:34 AM, Michiel Beijen wrote: > On Tue, Nov 14, 2017 at 11:07 AM, wrote: > > > 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 > >

Re: Bugtracker DBD::mysql

2017-11-14 Thread Michiel Beijen
On Tue, Nov 14, 2017 at 11:07 AM, wrote: > 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.

Re: Bugtracker DBD::mysql

2017-11-14 Thread pali
On Tuesday 14 November 2017 10:56:58 Michiel Beijen wrote: > Hi Pali, > > On Mon, Nov 13, 2017 at 6:18 PM, 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