Migrating to Github Issues
Jonathan "Duke" Leto
jonathan at leto.net
Fri Oct 21 18:57:16 UTC 2011
Howdy,
Net::Github + Net::Trac (as suggested by plobsing++) look like good
places to start.
Duke
On Thu, Oct 20, 2011 at 9:13 PM, Andy Lester <andy at petdance.com> wrote:
>> Do you think you can start prototyping a solution for an automatic migration? I
>> am thinking of something that you can actually test on a throwaway repo on
>> Github, so you can try to, for example, convert 10 Trac tickets to Issues and
>> see how the conversion works.
>
> Oh, sure, NOW come the implementation suggestions! :-)
>
> Yes, what you have suggested is exactly my plan, except I wasn't going to limit it to 10. The more data we put in a throwaway repo, the better.
>
> It'll be a while, I'm sure. I haven't even started sniffing around for pre-existing Trac->Github solutions.
>
> xoxo,
> Andy
>
>
> --
> Andy Lester => andy at petdance.com => www.petdance.com => AIM:petdance
>
>
--
Jonathan "Duke" Leto <jonathan at leto.net>
Leto Labs LLC
209.691.DUKE // http://labs.leto.net
NOTE: Personal email is only checked twice a day at 10am/2pm PST,
please call/text for time-sensitive matters.
More information about the parrot-dev
mailing list