)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"a7edc6aaefe9764d255d1d2b1ed93bea023dd8f3","unresolved":false,"context_lines":[{"line_number":7,"context_line":"ussuri: release sqlalchemy-migrate 0.13.0"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This release most just contains cleanups and officially"},{"line_number":10,"context_line":"adds support for python 3.5 and 3.6. It uses mysqlclient"},{"line_number":11,"context_line":"rather than the old MySQL-Python."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Note this is the first release since the repo moved from"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"3fa7e38b_7eac0a35","line":10,"updated":"2019-10-21 16:16:33.000000000","message":"Hmm, no 3.7 yet?","commit_id":"ebda55aafb983755c166c8aaf39debf04d085a69"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"81eb8824a7cd54a7b4808e449c11831141fc096c","unresolved":false,"context_lines":[{"line_number":7,"context_line":"ussuri: release sqlalchemy-migrate 0.13.0"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"This release most just contains cleanups and officially"},{"line_number":10,"context_line":"adds support for python 3.5 and 3.6. It uses mysqlclient"},{"line_number":11,"context_line":"rather than the old MySQL-Python."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Note this is the first release since the repo moved from"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"3fa7e38b_f4781990","line":10,"in_reply_to":"3fa7e38b_7eac0a35","updated":"2019-10-21 17:23:34.000000000","message":"Nope, but it probably works, just need to push a patch to add the py37 job template and update tox.ini.","commit_id":"ebda55aafb983755c166c8aaf39debf04d085a69"}],"deliverables/_independent/sqlalchemy-migrate.yaml":[{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"a7edc6aaefe9764d255d1d2b1ed93bea023dd8f3","unresolved":false,"context_lines":[{"line_number":84,"context_line":"      - repo: x/sqlalchemy-migrate"},{"line_number":85,"context_line":"        hash: 5d1f322542cd8eb42381612765be4ed9ca8105ec"},{"line_number":86,"context_line":"repository-settings:"},{"line_number":87,"context_line":"  openstack/sqlalchemy-migrate: {}"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"3fa7e38b_5e74aed0","line":87,"range":{"start_line":87,"start_character":2,"end_line":87,"end_character":11},"updated":"2019-10-21 16:16:33.000000000","message":"I wonder if we will have to update this to the new namespace too. Which would probably mean updating all instances in this file as well. Guess we can watch it and see. Current validation is happy, I am just wondering if any of the release-post processing could run into an issue.","commit_id":"ebda55aafb983755c166c8aaf39debf04d085a69"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"dc7371a9321a5d65be9e6b071f853de736ae001a","unresolved":false,"context_lines":[{"line_number":84,"context_line":"      - repo: x/sqlalchemy-migrate"},{"line_number":85,"context_line":"        hash: 5d1f322542cd8eb42381612765be4ed9ca8105ec"},{"line_number":86,"context_line":"repository-settings:"},{"line_number":87,"context_line":"  openstack/sqlalchemy-migrate: {}"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"3fa7e38b_35abfa1e","line":87,"range":{"start_line":87,"start_character":2,"end_line":87,"end_character":11},"in_reply_to":"3fa7e38b_5e74aed0","updated":"2019-10-22 18:34:21.000000000","message":"Yeah I think this will need to be updated but I\u0027m also okay with leaving it as is and seeing what breaks","commit_id":"ebda55aafb983755c166c8aaf39debf04d085a69"}]}