)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":14611,"name":"dasm","display_name":"dasm","email":"dsmigiel@redhat.com","username":"dasm"},"change_message_id":"035e4fa9cc6b0b206e38f118fb55617f3242b4f7","unresolved":false,"context_lines":[{"line_number":9,"context_line":"To avoid wide breakage when a new release of neutron-lib"},{"line_number":10,"context_line":"is published, a trick can be exploited in order to catch"},{"line_number":11,"context_line":"the failures ahead of time. This patch documents the"},{"line_number":12,"context_line":"trick as conceived by dougwig\u0027s diabolical mind."},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Change-Id: I301ff9f945eeb1a90be63d6610f375627f077aa8"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3aaa91ec_771bfe80","line":12,"range":{"start_line":12,"start_character":0,"end_line":12,"end_character":48},"updated":"2016-06-28 23:57:46.000000000","message":":D","commit_id":"5171f271e570f4e75e17951dd4113366b436b763"}],"doc/source/releasing.rst":[{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"2cf7e95bd12dc355263517b74fab501775f6a95a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1aa78d24_a6613c07","updated":"2016-07-07 13:56:36.000000000","message":"There are probably some other things worth mentioning W/R/T releasing. \n\n\nFor example:\n- Checking for any public API signature changes and ensuring we are adhering to our deprecation public API conventions. There\u0027s some work going on to generate such a report here: https://review.openstack.org/#/c/338571/\n- Ensuring any new (added in since the last release of neutron-lib) public APIs are tip-top. Once we publish an API we are stuck with it (as per our deprecation process) for awhile, so this window before the release is critical for solidifying anything (publicly) new.\n\nI\u0027m fine with trying to push separate additional patch(es) for the above and leave this patch as-is.\n\n\nAlso, is it worth linking to the release process [1] and perhaps a sample release request patch [2]?\n\n[1] https://github.com/openstack/releases\n[2] https://review.openstack.org/#/c/306575/","commit_id":"5171f271e570f4e75e17951dd4113366b436b763"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"de460fe17198910f9c9fb718174d70eb93d3aa08","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1aa78d24_603a6e36","in_reply_to":"1aa78d24_a6613c07","updated":"2016-07-13 23:28:35.000000000","message":"I was not going to elaborate further. Feel free to follow up.","commit_id":"5171f271e570f4e75e17951dd4113366b436b763"},{"author":{"_account_id":5367,"name":"boden","email":"bodenvmw@gmail.com","username":"boden"},"change_message_id":"2cf7e95bd12dc355263517b74fab501775f6a95a","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Before you intend to release a new version of neutron-lib consider posting"},{"line_number":6,"context_line":"a `sentinel patch \u003chttps://review.openstack.org/#q,I261ec7ea9a5443fd23b806df8c1a109049264fcb,n,z\u003e`_"},{"line_number":7,"context_line":"that will allow to validate that the neutron-lib hash chosen for tagging is"},{"line_number":8,"context_line":"not breaking any of the jobs affecting a project you care about, first"},{"line_number":9,"context_line":"and foremost Neutron. As the patch shows, upper-constraints must be bypassed"},{"line_number":10,"context_line":"and that may itself lead to failures due to upstream package changes. In that"},{"line_number":11,"context_line":"case consider hard-coding a dummy upper-constraints file that itself uses"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1aa78d24_113208a7","line":8,"range":{"start_line":8,"start_character":24,"end_line":8,"end_character":63},"updated":"2016-07-07 13:56:36.000000000","message":"Might a tox target/tool that submits a sentinel patch for all neutron core/stadium projects be helpful to automate this? Kind of a consumer \"smoke test\" if you will.","commit_id":"5171f271e570f4e75e17951dd4113366b436b763"},{"author":{"_account_id":748,"name":"Armando Migliaccio","email":"armamig@gmail.com","username":"armando-migliaccio"},"change_message_id":"de460fe17198910f9c9fb718174d70eb93d3aa08","unresolved":false,"context_lines":[{"line_number":5,"context_line":"Before you intend to release a new version of neutron-lib consider posting"},{"line_number":6,"context_line":"a `sentinel patch \u003chttps://review.openstack.org/#q,I261ec7ea9a5443fd23b806df8c1a109049264fcb,n,z\u003e`_"},{"line_number":7,"context_line":"that will allow to validate that the neutron-lib hash chosen for tagging is"},{"line_number":8,"context_line":"not breaking any of the jobs affecting a project you care about, first"},{"line_number":9,"context_line":"and foremost Neutron. As the patch shows, upper-constraints must be bypassed"},{"line_number":10,"context_line":"and that may itself lead to failures due to upstream package changes. In that"},{"line_number":11,"context_line":"case consider hard-coding a dummy upper-constraints file that itself uses"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1aa78d24_2038663d","line":8,"range":{"start_line":8,"start_character":24,"end_line":8,"end_character":63},"in_reply_to":"1aa78d24_113208a7","updated":"2016-07-13 23:28:35.000000000","message":"Automation pays itself for very frequent changes, I am not sure we\u0027re at that inflection point yet.","commit_id":"5171f271e570f4e75e17951dd4113366b436b763"}]}
