On 2017-03-02 7:06 PM, Brett Cannon wrote:
The discussion of automating the creation of cherry-pick PRs is at https://github.com/python/core-workflow/issues/8. And the requirement of the PR is to force people to go through CI to verify the cherry-pick took cleanly (and the Travis config is structured to only run the test suite if the PR changes things outside of Doc/; same goes for building the docs and code coverage is never waited on).
The issue here is that we now don't seem to trust core devs to check if cherry-picks are good and working. In an ideal world where online tooling spends as much time as running the test suite locally it would work flawlessly. In the reality, it simply takes a lot of time *waiting* and is quite distracting. Anyways, this is just my 2 cents. Maybe I just need more time to get accustomed to the new process. Thanks, Yury _______________________________________________ core-workflow mailing list core-workflow@python.org https://mail.python.org/mailman/listinfo/core-workflow This list is governed by the PSF Code of Conduct: https://www.python.org/psf/codeofconduct
