[perl #128520] [META][RT][RFC] Consider migrating from RT

2018-03-08 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
OK, there's now a follow-up ticket here:
https://github.com/rakudo/rakudo/issues/1598

On 2018-03-08 00:39:56, steve.myn...@gmail.com wrote:
> Maybe the ticket should be closed if/when the RT bug tracker is closed
> to new tickets itself and references to RT removed from all docs?
>
> S
>
> On 5 March 2018 at 17:50, Zoffix Znet via RT
>  wrote:
> > On Wed, 11 Oct 2017 13:22:50 -0700, alex.jakime...@gmail.com wrote:
> >> Oh, and if rakudo/issues is opened, then for me all issues raised in
> >> this
> >> ticket will be resolved.
> >
> > It was opened awhile ago.
> >
> > …and based on the recent usage, seems GitHub's ticket tracker is
> > preferred by users, so as far as this ticket goes, I think it can be
> > closed.


Re: [perl #128520] [META][RT][RFC] Consider migrating from RT

2018-03-08 Thread Steve Mynott
Maybe the ticket should be closed if/when the RT bug tracker is closed
to new tickets itself and references to RT removed from all docs?

S

On 5 March 2018 at 17:50, Zoffix Znet via RT
 wrote:
> On Wed, 11 Oct 2017 13:22:50 -0700, alex.jakime...@gmail.com wrote:
>> Oh, and if rakudo/issues is opened, then for me all issues raised in this
>> ticket will be resolved.
>
> It was opened awhile ago.
>
> …and based on the recent usage, seems GitHub's ticket tracker is preferred by 
> users, so as far as this ticket goes, I think it can be closed.



-- 
Steve Mynott 
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5


Re: [perl #128520] [META][RT][RFC] Consider migrating from RT

2018-03-08 Thread Steve Mynott via RT
Maybe the ticket should be closed if/when the RT bug tracker is closed
to new tickets itself and references to RT removed from all docs?

S

On 5 March 2018 at 17:50, Zoffix Znet via RT
 wrote:
> On Wed, 11 Oct 2017 13:22:50 -0700, alex.jakime...@gmail.com wrote:
>> Oh, and if rakudo/issues is opened, then for me all issues raised in this
>> ticket will be resolved.
>
> It was opened awhile ago.
>
> …and based on the recent usage, seems GitHub's ticket tracker is preferred by 
> users, so as far as this ticket goes, I think it can be closed.



-- 
Steve Mynott 
cv25519/ECF8B611205B447E091246AF959E3D6197190DD5


[perl #128520] [META][RT][RFC] Consider migrating from RT

2018-03-05 Thread Zoffix Znet via RT
On Wed, 11 Oct 2017 13:22:50 -0700, alex.jakime...@gmail.com wrote:
> Oh, and if rakudo/issues is opened, then for me all issues raised in this
> ticket will be resolved.

It was opened awhile ago.

…and based on the recent usage, seems GitHub's ticket tracker is preferred by 
users, so as far as this ticket goes, I think it can be closed.


[perl #128520] [META][RT][RFC] Consider migrating from RT

2018-03-05 Thread Zoffix Znet via RT
On Wed, 11 Oct 2017 13:22:50 -0700, alex.jakime...@gmail.com wrote:
> Oh, and if rakudo/issues is opened, then for me all issues raised in this
> ticket will be resolved.

It was opened awhile ago.

…and based on the recent usage, seems GitHub's ticket tracker is preferred by 
users, so as far as this ticket goes, I think it can be closed.


[perl #128520] [META][RT][RFC] Consider migrating from RT

2017-10-11 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
Oh, and if rakudo/issues is opened, then for me all issues raised in this
ticket will be resolved.

On 2017-10-11 13:21:41, alex.jakime...@gmail.com wrote:
> There was some fresh discussion on this topic recently. See
> https://irclog.perlgeek.de/perl6-dev/2017-10-11#i_15289848 and the
> start of the
> discussion on https://irclog.perlgeek.de/perl6-dev/2017-10-
> 11#i_15289680
>
> The idea is that instead of doing a full migration we can just start
> using
> another tracker in parallel, and then we'll see how it goes.


[perl #128520] [META][RT][RFC] Consider migrating from RT

2017-10-11 Thread Aleks-Daniel Jakimenko-Aleksejev via RT
There was some fresh discussion on this topic recently. See
https://irclog.perlgeek.de/perl6-dev/2017-10-11#i_15289848 and the start of the
discussion on https://irclog.perlgeek.de/perl6-dev/2017-10-11#i_15289680

The idea is that instead of doing a full migration we can just start using
another tracker in parallel, and then we'll see how it goes.