<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 6, 2016 at 9:41 PM, Brett Cannon <span dir="ltr"><<a href="mailto:brett@snarky.ca" target="_blank">brett@snarky.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">As always, the master TODO list is kept at <a href="https://www.python.org/dev/peps/pep-0512/#cpython-repo" target="_blank">https://www.python.org/dev/<wbr>peps/pep-0512/#cpython-repo</a> . To summarize:<div><ul><li>The <a href="http://bugs.python.org" target="_blank">bugs.python.org</a> changes have patches but they need to land (hopefully Maciej Szulik or R. David Murray can help with that)<br></li></ul></div></div></blockquote><div>I'll sync with David and Ezio about it and will keep my hand on it. I don't have commit rights to<br></div><div>roundup repos ;)<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><ul><li></li><li>Ned Deily and R. David said they could help with the IRC and emails to python-checkins at the core dev sprint last month (unless I'm remembering wrong :)</li><li>Ned said PEP 101 will get updated by him</li><li>sys._git is coded but awaiting a code review by Ned (and probably deciding if it should be in Python 3.6 or just straight into 3.7)</li><li>Updating <a href="http://hg.python.org/lookup" target="_blank">hg.python.org/lookup</a> is still needed/desired</li><li>Need to check if the current mirror is actually good enough to just keeping using to avoid breaking everyone's clone of the repository, or if we truly do need to fully regenerate the repo</li><li>Need to finish updating the devguide</li></ul><div><br></div></div><div>So a bunch of stuff is in-progress which is great! Probably the thing that I need the most help with ATM is updating the devguide. There's a `github` branch at <a href="https://github.com/python/devguide/tree/github" target="_blank">https://github.com/python/<wbr>devguide/tree/github</a> where we're trying to eliminate or move mentions of Mercurial over to Git (see <a href="https://github.com/python/devguide/milestone/1" target="_blank">https://github.com/<wbr>python/devguide/milestone/1</a> <wbr>for the relevant issues). We also need to figure out exactly what git commands we want for doing squash commits from the command-line (we will have the Squash and Merge button on GitHub, but some people prefer a CLI and the commands that GitHub provides are not squash ones), and we also need instructions on how to cherrypick a change that went into master but needs to be backported to an older version(s) of Python (I will start separate threads for that discussion).</div></div></blockquote><div><br></div><div>I can create a doc describing the cherry-pick, should I post a PR against that branch? <br><br></div><div>The general flow should be very simple, such as:<br></div><div>1. find the commit you want to cherry-pick<br></div><div>2. switch to branch you're cherry-picking to<br></div><div>3. git cherry-pick sha<br></div><div>4. fix eventual incompatibilities<br><br></div><div>With more words, that should be ok, wdyt?<br> <br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><br></div><div>At the core sprints last month, Ned and I talked and we agreed that we wouldn't switch until after 3.6.0 came out so as to not risk botching the release because of the migration. That means the switchover won't happen any sooner than mid/late December, but luckily most of this stuff can still be done (and tested) prior to officially switching so this doesn't need to hold anything up.</div></div>
</blockquote></div><br></div></div>