On 2017-05-02 20:28, Terry Reedy wrote: > On 5/2/2017 10:07 AM, R. David Murray wrote: >> On Tue, 02 May 2017 09:36:02 +0200, "M.-A. Lemburg" <m...@egenix.com> >> wrote: > >>> IMO, it's much easier for everyone to just always point people >>> to BPO for discussions and keep PRs reserved for code reviews. >> >> I agree with Mark-Andre here. It will take effort on our part to >> make our culture be "discuss on BPO", but it will produce a much >> superior history to what github PRs produce, so I think it is worth it. > > It would easier to move discussion to bpo if there were a clickable link > from PR to bpo, just as there is in the opposite direction. I believe > that there is a workflow issue to add this, but last I knew, it was > bogged down in where to put the link, or something.
All recent PRs have a clickable link to BPO. It's in the box with CI results. Click on "Details" for "bedevere/issue-number". Christian _______________________________________________ python-committers mailing list python-committers@python.org https://mail.python.org/mailman/listinfo/python-committers Code of Conduct: https://www.python.org/psf/codeofconduct/
