Message293449
I'm not sure if this is going to be useful enough to force all contributors to deal with. Justification for a change should be on bugs.python.org and that's mentioned in the CONTRIBUTING.md guidelines. As for testing, the Travis/AppVeyor failures should communicate that. And for specifying the issue number, there's a status check for that to help communicate it.
I'll let other core devs comment, but while I appreciate what Jensen is trying to help with, I don't think the template helps enough to justify forcing every contributor to have to deal with it.
You can also bring this up on the core-workflow mailing list, Jensen, if you want to discuss it there. |
|
Date |
User |
Action |
Args |
2017-05-10 19:19:39 | brett.cannon | set | recipients:
+ brett.cannon, Jensen Taylor |
2017-05-10 19:19:38 | brett.cannon | set | messageid: <1494443978.99.0.0776372440919.issue30336@psf.upfronthosting.co.za> |
2017-05-10 19:19:38 | brett.cannon | link | issue30336 messages |
2017-05-10 19:19:38 | brett.cannon | create | |
|