Re: [Ironpython-users] Codeplex -> GitHub Issue Migration (Was: Differences with pyc-compiled assemblies?)

2012-11-24 Thread Slide
I also just realized that my import of labels (components in CodePlex speak) and milestones (releases in CodePlex speak) is not working correctly. I'll fix that as well. On Sat, Nov 24, 2012 at 8:41 PM, Slide wrote: > Take a look at https://github.com/slide/test/issues?state=open and let me > k

Re: [Ironpython-users] Codeplex -> GitHub Issue Migration (Was: Differences with pyc-compiled assemblies?)

2012-11-24 Thread Slide
Take a look at https://github.com/slide/test/issues?state=open and let me know what you think. I know I need to reverse the order of the comments once imported to GitHub, so don't look at that, but tell me what you think about the data I am importing and the format as well. Attachments are kind of

[Ironpython-users] Codeplex -> GitHub Issue Migration (Was: Differences with pyc-compiled assemblies?)

2012-11-24 Thread Jeff Hardy
The completist in me would like to see everything moved, but I would be quite happy with just the open issues. I'm OK with losing who it's assign to and what the target release is, but I would hate to lose comments or attached files. If possible I'd like to keep the user who created/commented, but

Re: [Ironpython-users] Differences with pyc-compiled assemblies?

2012-11-24 Thread Slide
Are we wanting to migrate all closed issues as well, or just the ones that are open? I tried using that script I found and it wasn't very robust. I have written something that pulls out quite a bit of information from the CodePlex issues site into a sqlite database and then I can import into GitHub