<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 10, 2017, at 5:13 PM, Brett Cannon <<a href="mailto:brett@python.org" class="">brett@python.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">I can't believe it's been 4 weeks. It feels like it was ages/yesterday when we moved. :)<div class=""><br class=""></div><div class="">First, I hope people are not regretting letting/having me make this migration. I know there have been some things to work through (and others still to come), but I hope this is all a net positive (either now or in the near future).</div><div class=""><br class=""></div><div class="">Second, I wanted to get initial feedback on things we can easily tweak:</div><div class=""><ul class=""><li class="">Requiring Travis to pass (I <b class="">really</b> don't want to turn this off as we already had a broken build when I temporarily turned it off at someone's request when Travis was backed up from the AWS S3 outage; I also don't plan to make AppVeyor required unless there's a way to make it be skipped for doc-only changes)</li></ul></div></div></div></blockquote><div><br class=""></div><div>I agree with not wanting to turn off mandatory CI. It’d be nice to get as much coverage of platforms as we can as required CI on a per-merge basis, but there is obviously a balance to be had here between quick responses and maximal coverage.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><ul class=""><li class="">Cherry-picking working out? (We can go back to forward merging if people really want to, but I think long-term cherry-picking will allow for more automation)</li><ul class=""><li class="">Along with that, are the labels for cherry-picking working out? (Some devs seem to like using title labels like `[3.6]` to flag cherry-picks so it's more obvious in emails so I don't know if the labels are really that useful)</li></ul></ul></div></div></div></blockquote><div><br class=""></div><div>For the couple of things I’ve done I’ve not had any problem with it.</div><div><br class=""></div><div>One thing I noticed that might be weird is that Misc/NEWS is kind of weird now. On `master` it only contains entries for 3.6 up until the point that 3.6 was branched off of `master` (or more specifically in this case, since we migrated to a cherry-picking work flow). This will likely cause some issues now that I think about it with the stuff in #python/core-workflow#6 because files added to `master` between the last release of X.Y and when X.Y gets branched off of `master` are going to show up as new in X.Y+1. This could be resolved I think by, immediately altering branching X.Y off of `master`, deleting all pending news files and also cherry-picking the “compile” step of say, 3.6 into the `master` branch (and so on up the line). Alternatively still do the delete thing, but make the ``Misc/NEWS`` specific to a particular release series.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><ul class=""><li class="">Is the mention bot helpful? (Our config is at <a href="https://github.com/python/cpython/blob/master/.mention-bot" class="">https://github.com/python/cpython/blob/master/.mention-bot</a> and the docs are at <a href="https://github.com/facebook/mention-bot" class="">https://github.com/facebook/mention-bot</a>)</li></ul></div></div></div></blockquote><div><br class=""></div><div>I’ve found it helpful thus far. It’s poked me on a few issues and I jumped in and gave a review on them. There is too much churn in python/cpython for me to get notified of every issue. I suspect as we get more people submitting PRs (and thus, retaining author) it will get more diverse in who it notifies as well.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><ul class=""><li class="">Anything to tweak about the coverage bot and reports? (Our config is at <a href="https://github.com/python/cpython/blob/master/.codecov.yml" class="">https://github.com/python/cpython/blob/master/.codecov.yml</a> and docs at <a href="https://docs.codecov.io/docs/codecov-yaml" class="">https://docs.codecov.io/docs/codecov-yaml</a>)</li></ul><div class="">Third, I wanted to point out some of the more critical discussions going on at <a href="https://github.com/python/core-workflow/issues" class="">https://github.com/python/core-workflow/issues</a>. Specifically, <a href="https://github.com/python/core-workflow/issues/6" class="">https://github.com/python/core-workflow/issues/6</a> is working towards a solution for Misc/NEWS so if you care about the final solution you should participate there. After Misc/NEWS is solved the next step becomes solving the cherry-picking overhead with a more automated approach. We are also discussing closed branches to make the list of branches more manageable at <a href="https://github.com/python/core-workflow/issues/31" class="">https://github.com/python/core-workflow/issues/31</a>.</div></div><div class=""><br class=""></div><div class="">Fourth, the lack of messages showing up on <a href="http://bugs.python.org/" class="">bugs.python.org</a> after a commit is being tracked at <a href="http://psf.upfronthosting.co.za/roundup/meta/issue613" class="">http://psf.upfronthosting.co.za/roundup/meta/issue613</a>. I'm sure Ezio and Maciej would appreciate any help people may be able to volunteer to help in solving the problem.</div><div class=""><br class=""></div><div class="">Fifth, anything I missed? :)</div></div>
_______________________________________________<br class="">python-committers mailing list<br class=""><a href="mailto:python-committers@python.org" class="">python-committers@python.org</a><br class="">https://mail.python.org/mailman/listinfo/python-committers<br class="">Code of Conduct: https://www.python.org/psf/codeofconduct/</div></blockquote></div><br class=""><div class="">
<div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class="">—<br class="">Donald Stufft<br class=""></div><div style="color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant-ligatures: normal; font-variant-position: normal; font-variant-caps: normal; font-variant-numeric: normal; font-variant-alternates: normal; font-variant-east-asian: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>