Assuming you can't commit to Mercurial anymore and the next email from me
will either be an introduction email to our new workflow or me apologizing
for something going horribly wrong. Either way I'm hoping you will hear
from me later today. :)
To keep things simple, just assume you should not commit to Mercurial on
Feb 10 no matter your timezone. The hope is that the migration will go
smoothly enough that commits can be accepted starting on Feb 11 (or sooner;
I'll email once everything has moved over). The only thing that might take
a couple of days to straighten out is the building of docs.python.org (it's
planned to happen on Friday, but if the devguide was any indication there
will be some unforseen hiccup). Also realize that the current cpython
mirror on GitHub won't survive the migration, so plan to generate patches
for any clones you have to move to the new repo (and Victor should plan to
have his PRs get closed on the mirror).
I will be writing a doc that outlines the key changes in how things will be
handled so people can get started quickly. The devguide will also be
appropriately updated (it's mostly already updated and can be seen at
https://cpython-devguide.readthedocs.io/en/github/, but there's one change
that it doesn't cover in regards to specifying issue numbers).
All the blockers for migrating to GitHub are done! That means it's time to
schedule the migration. Are there any days that people would really prefer
we *don't* do the migration on? I'm hoping to do it next week and
definitely this month. I have already asked Ned and Larry and they are fine
with any date this month. So if there's some date people don't want the
migration to happen on (e.g. running a sprint), please speak up. Otherwise
I will schedule among those helping me with the migration and get this done!
Thank you all, for inviting me here. It's a real honor.
I still have a lot to learn from all of you, and I realize that the real
hard work is just starting now.
But at least I was promised a fun club to be in ;)
Looking forward contributing more and working with everyone here :)
Raymond, Guido, thank you again for taking me under your wing.