)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"2de39dec2dc0725049c42423bbbdc3e519424d9a","unresolved":false,"context_lines":[{"line_number":29,"context_line":"   pick the version of the payload they receive. It\u0027s probably also"},{"line_number":30,"context_line":"   worth considering that if we\u0027re going to bump the major version"},{"line_number":31,"context_line":"   on this at some point, it\u0027s probably best to do that before we"},{"line_number":32,"context_line":"   ever even officially release the thing."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"2. Just call this a mulligan and remove the fields and leave the"},{"line_number":35,"context_line":"   version as 1.0, essentially a partial revert of the change. The"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"5fc1f717_618d2329","line":32,"updated":"2019-04-04 06:16:49.000000000","message":"I vote for this alternative. So bump to 2.0 and drop the fields. Even if there is a consumer for 1.0 we at least indicate with the version number bump that something is changing.","commit_id":"d616dbc576d87a12561381580a2b3fce4716b4f5"},{"author":{"_account_id":26936,"name":"Surya Seetharaman","email":"suryaseetharaman.9@gmail.com","username":"tssurya"},"change_message_id":"5c06abf6639ae13ebbffa8b3f6542ac74b16d950","unresolved":false,"context_lines":[{"line_number":29,"context_line":"   pick the version of the payload they receive. It\u0027s probably also"},{"line_number":30,"context_line":"   worth considering that if we\u0027re going to bump the major version"},{"line_number":31,"context_line":"   on this at some point, it\u0027s probably best to do that before we"},{"line_number":32,"context_line":"   ever even officially release the thing."},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"2. Just call this a mulligan and remove the fields and leave the"},{"line_number":35,"context_line":"   version as 1.0, essentially a partial revert of the change. The"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"5fc1f717_120b4e24","line":32,"in_reply_to":"5fc1f717_618d2329","updated":"2019-04-04 08:44:28.000000000","message":"\u003e I vote for this alternative. So bump to 2.0 and drop the fields.\n\n++\n\n \u003e Even if there is a consumer for 1.0 we at least indicate with the\n \u003e version number bump that something is changing.\n\nhmm, is there any harm in changing this for 1.0 since we know nobody is consuming them (we could announce this or something) ? Forgive me if its really a stupid idea with regards to the whole concept of versioning. I agree with melwitt that its bad we would allow users even in the future to opt into 1.0 that would still have this flaw. We should probably warn the users using 19.0.0.0rc1 in the notification docs and link the security impact bug.","commit_id":"d616dbc576d87a12561381580a2b3fce4716b4f5"}]}