Message13062

As in PEP-512 (https://www.python.org/dev/peps/pep-0512/) and for much the same reasons, we've said we'd migrate to GitHub. This seems the apposite time, before we get started on bug-fixes and Jython 3. This implicitly includes using git rather than mercurial in the development environment.

I'm tentatively assigning myself the ticket. I have a bit of experience now with git, so can probably manage this without making too much of a mess. The main difficulty is to avoid something that works but has some fearful drawback later on. I'll dry run it in my own space first, fix a bug in the dry, then repeat for real. If anyone knows a lot about this, help would be welcome.

Fortunately, CPython have done this before us. (And lots of others, but they're nearest, and in public.) Discussion on the core-workflow list begins around the start of 2016.
https://mail.python.org/archives/list/core-workflow@python.org/2016/1/
This is something like the final plan:
https://mail.python.org/archives/list/core-workflow@python.org/thread/NZDI44KRG7NUYI2PDHPDW6ZXQTAJZ7P7/


We shouldn't expect to get the same tool integration as CPython (e.g. updating bugs.jython.org with changes on GitHub). We'd have easier use of tools supporting the development process if we were in the Python organisation, from GitHub's POV. If we can work as well as now, haven't dropped any critical information, and can merge PRs via GitHub, I would count that a success.

There will be several details to take care of, some general to Python, some specific to Jython. I doubt I will spot them all first time. Here's a start ...


In the generic category:

* Converting the repo (history, contributor names etc.): https://mail.python.org/archives/list/core-workflow@python.org/thread/KXSKDHUOSGX6WSSH54I7HIH33SDLYBIW/

* Contributor names: 

* sys._git: https://bugs.python.org/issue27593

* git and new lines: https://bugs.python.org/issue27425


Specific to Jython:

* Continue building with ant, with minimal change, but using git in place of (i.e. no longer supporting) hg to get version control information. (git must be available on the path or you get an uncontrolled snapshot of some kind.)

* Have concurrent branches like CPython and the dev-guide. (We haven't really done that, but need to, in a small way.)