Re: Changes coming to CPython's code hosting

2016-01-03 12:14 GMT+02:00 Darjus Loktevic <[email protected]>:
>
> Personally i don't mind moving issues to github (not sure we can actually
> move them), but i would hate for us to lose all the years of history. We
> need to discuss this internally, though i think we should follow what
> CPython is doing.

I would also prefer GitHub tracker. It's not the best tracker I've
used, but I consider it a lot better than Roundup, and it obviously
has the best GitHub integration possible. If I've understood it
correctly, the main reason it won't be used with CPython are vendor
lock-in related. I doubt are such worries relevant with Jython, and in
the worst case GitHub APIs allow getting the issue data at least in
some format. I understand the value for Jython using same the process
than CPython, though.

I have promised earlier on IRC and when I met with Jim last spring in
Colorado, that I can help migrating existing issues from Roundup to
GitHub if we decide to fully move Jython to GitHub. I've done similar
migration when we moved Robot Framework from Google Code to GitHub.
Due to being busy with work and family I didn't have time to look at
that last autumn, but I ought to have time for it now if needed.

Cheers,
    .peke
-- 
Agile Tester/Developer/Consultant :: http://eliga.fi
Lead Developer of Robot Framework :: http://robotframework.org

------------------------------------------------------------------------------