)]}'
{"doc/source/contributor/release-notes.rst":[{"author":{"_account_id":21420,"name":"Gage Hugo","email":"gagehugo@gmail.com","username":"ghugo"},"change_message_id":"50c47f3f63d5a8b5835600a92c2820594e66ff36","unresolved":false,"context_lines":[{"line_number":35,"context_line":""},{"line_number":36,"context_line":"    We highly recommend taking careful thought when writing and reviewing"},{"line_number":37,"context_line":"    release notes. Once a release note has been published with a formal"},{"line_number":38,"context_line":"    release, casually updating it can cause it to be published in a subsequent"},{"line_number":39,"context_line":"    release. Reviews that update, or modify, a release note from a previous"},{"line_number":40,"context_line":"    release outside of the branch it was added in should be rejected unless"},{"line_number":41,"context_line":"    it\u0027s required for a very specific case."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f287b81_996c6e09","line":38,"range":{"start_line":38,"start_character":34,"end_line":38,"end_character":37},"updated":"2017-08-23 01:23:45.000000000","message":"could replace \"can\" with \"will\" since this is how we got here","commit_id":"0e30adf7d2e61e92e106e3c9caf4d16b3e5140ed"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"16735ea7f3c450cab226d9c831c6ef644594953c","unresolved":false,"context_lines":[{"line_number":35,"context_line":""},{"line_number":36,"context_line":"    We highly recommend taking careful thought when writing and reviewing"},{"line_number":37,"context_line":"    release notes. Once a release note has been published with a formal"},{"line_number":38,"context_line":"    release, casually updating it can cause it to be published in a subsequent"},{"line_number":39,"context_line":"    release. Reviews that update, or modify, a release note from a previous"},{"line_number":40,"context_line":"    release outside of the branch it was added in should be rejected unless"},{"line_number":41,"context_line":"    it\u0027s required for a very specific case."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f287b81_16f5eecb","line":38,"range":{"start_line":38,"start_character":13,"end_line":38,"end_character":21},"updated":"2017-08-23 01:00:39.000000000","message":"remove \u0027casually\u0027","commit_id":"0e30adf7d2e61e92e106e3c9caf4d16b3e5140ed"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"b01b95f1fa2c258a4cddb9058be4e2e236330889","unresolved":false,"context_lines":[{"line_number":35,"context_line":""},{"line_number":36,"context_line":"    We highly recommend taking careful thought when writing and reviewing"},{"line_number":37,"context_line":"    release notes. Once a release note has been published with a formal"},{"line_number":38,"context_line":"    release, casually updating it can cause it to be published in a subsequent"},{"line_number":39,"context_line":"    release. Reviews that update, or modify, a release note from a previous"},{"line_number":40,"context_line":"    release outside of the branch it was added in should be rejected unless"},{"line_number":41,"context_line":"    it\u0027s required for a very specific case."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f287b81_32f0e1c9","line":38,"in_reply_to":"7f287b81_16f5eecb","updated":"2017-08-23 13:39:39.000000000","message":"Done","commit_id":"0e30adf7d2e61e92e106e3c9caf4d16b3e5140ed"},{"author":{"_account_id":5046,"name":"Lance Bragstad","email":"lbragstad@redhat.com","username":"ldbragst"},"change_message_id":"b01b95f1fa2c258a4cddb9058be4e2e236330889","unresolved":false,"context_lines":[{"line_number":35,"context_line":""},{"line_number":36,"context_line":"    We highly recommend taking careful thought when writing and reviewing"},{"line_number":37,"context_line":"    release notes. Once a release note has been published with a formal"},{"line_number":38,"context_line":"    release, casually updating it can cause it to be published in a subsequent"},{"line_number":39,"context_line":"    release. Reviews that update, or modify, a release note from a previous"},{"line_number":40,"context_line":"    release outside of the branch it was added in should be rejected unless"},{"line_number":41,"context_line":"    it\u0027s required for a very specific case."}],"source_content_type":"text/x-rst","patch_set":1,"id":"7f287b81_12ede5ee","line":38,"in_reply_to":"7f287b81_996c6e09","updated":"2017-08-23 13:39:39.000000000","message":"Done","commit_id":"0e30adf7d2e61e92e106e3c9caf4d16b3e5140ed"}]}