)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":21129,"name":"Alan Bishop","email":"abishopsweng@gmail.com","username":"ASBishop","status":"ex Red Hat"},"change_message_id":"5310ade11f84a352c5327604d4fc708e0c22f2fe","unresolved":true,"context_lines":[{"line_number":17,"context_line":"... which most of us do.  But the wider community, as far as I can"},{"line_number":18,"context_line":"tell, thinks that requirement is unreasonable and that it would"},{"line_number":19,"context_line":"discourage new contributors."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"This requires a corresponding change in the zuul config file so that"},{"line_number":22,"context_line":"the functional-py36 job explicitly requires that py36 be available."},{"line_number":23,"context_line":"And because explicit is better than implicit, the requirement is also"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"502c4d86_e9855f7c","line":20,"updated":"2021-06-18 15:52:33.000000000","message":"I can see that point of view. Developers are free to test locally with any py3 they happen to have lying around, as long as they understand patches are specifically tested against py36 and py38.","commit_id":"24d30a384ea81b7b0b462d56a3d5a0c85022ca47"}]}