)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"f5367e2afd425b277859ac8ade751e9ea7f0bfc3","unresolved":false,"context_lines":[{"line_number":19,"context_line":"an fresh flow is installed."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"UpgradeImpact"},{"line_number":22,"context_line":"DocImpact: _notification_host in L2populationAgentNotifyAPI now"},{"line_number":23,"context_line":"           is a blocking operation."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"Closes-Bug: #1569795"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"3a461143_3a3cf6e1","line":22,"updated":"2017-01-26 19:55:09.000000000","message":"I don\u0027t see why a reader of user/ops docs would care. Is this tag justified?","commit_id":"2301258d3ccf110f5ddfeea00f0f9ed3c2496b74"}],"neutron/plugins/ml2/drivers/l2pop/rpc.py":[{"author":{"_account_id":1653,"name":"garyk","email":"gkotton@vmware.com","username":"garyk"},"change_message_id":"898ca5f04ad0712aeef26ba6da7061dfaba9ae6b","unresolved":false,"context_lines":[{"line_number":57,"context_line":"                   \u0027fdb_entries\u0027: fdb_entries})"},{"line_number":58,"context_line":""},{"line_number":59,"context_line":"        cctxt \u003d self.client.prepare(topic\u003dself.topic_l2pop_update, server\u003dhost)"},{"line_number":60,"context_line":"        cctxt.call(context, method, fdb_entries\u003dfdb_entries)"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"    def add_fdb_entries(self, context, fdb_entries, host\u003dNone):"},{"line_number":63,"context_line":"        if fdb_entries:"}],"source_content_type":"text/x-python","patch_set":1,"id":"5a18252c_4dc1cb53","line":60,"updated":"2016-04-14 10:54:05.000000000","message":"this is now a blocking operation.\n\nif you change this you need to do the following:\n1. update the commit message to indicate that the message functionality has changed. I think that this at least requires a docimpact flag. It must have an UpgradeIMPACT FLAG\n2. You need to change the message versions\n3. It also requires a release note\n\nHaving mentioned all of those i do not think that this is the correct way to go. But an ML2 maintainer can add her/his two cents","commit_id":"da5db9758421d90bd07338540ccd95d173094581"}]}
