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

Jeff Hardy jdhardy at gmail.com
Sun Nov 25 04:15:02 CET 2012

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 that might not be possible with the different
sets of users.

- Jeff

On Sat, Nov 24, 2012 at 4:04 PM, Slide <slide.o.mix at gmail.com> wrote:
> 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 issues. I just need to know what information we want to transfer and
> keep.
> On Tue, Nov 13, 2012 at 10:31 AM, Jeff Hardy <jdhardy at gmail.com> wrote:
>> On Mon, Nov 12, 2012 at 10:39 AM, Slide <slide.o.mix at gmail.com> wrote:
>> > Yes, codeplex has issues with pasting code, horrible horrible issues.
>> If anyone knows of a Codeplex -> GitHub issue migration script, I'd be
>> happy to hear about it.
>> - Jeff
> --
> Website: http://earl-of-code.com

More information about the Ironpython-users mailing list