Re: Bugtracker DBD::mysql

[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 the script I used when I tried the last time around
which did not work for me, I even send back a pull request for an
installation issue I encountered.
(https://github.com/houseabsolute/RTx-ToGitHub/pull/3)

This time I used dagoldens script:
https://github.com/dagolden/zzz-rt-to-github - it mostly worked but
there were some comments created by users who logged in on RT using
OpenID and where the user field started with 'http' and on which the
RT API seemed to choke. This was the dirty patch I used:

diff --git a/rt-to-github.pl b/rt-to-github.pl
index c6d20c8..06dca7e 100755
--- a/rt-to-github.pl
+++ b/rt-to-github.pl
@@ -63,6 +63,10 @@ sub _dist_name {

 sub _find_from {
 my ( $xact ) = @_;
+if ($xact->creator =~ /^http/) {
+# this is because the creator used OpenID
+return sprintf("From %s on %s", lc( $xact->creator), $xact->creat
ed);
+}

So as of today, *the* bug tracker for DBD::mysql is on Github at
https://github.com/perl5-dbi/DBD-mysql/issues and we no longer use RT!

--
Michiel

Re: Bugtracker DBD::mysql

[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,  > 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.
>
> 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.

Yeah, I'm sure this is *easier*. But I really hate the RT cpan bug
tracker, so I'd prefer to look again at migrating from RT >> Github -
if that really would not work for some reason I'll consider migrating
the other way around.


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


-Dan

Re: Bugtracker DBD::mysql

[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
> > 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.
>
> Yeah, I'm sure this is *easier*. But I really hate the RT cpan bug
> tracker, so I'd prefer to look again at migrating from RT >> Github -
> if that really would not work for some reason I'll consider migrating
> the other way around.
>
>
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

-Dan

Re: Bugtracker DBD::mysql

[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.
>
> 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.

Yeah, I'm sure this is *easier*. But I really hate the RT cpan bug
tracker, so I'd prefer to look again at migrating from RT >> Github -
if that really would not work for some reason I'll consider migrating
the other way around.

--
Michiel

Re: Bugtracker DBD::mysql

[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 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.