)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":6816,"name":"Jesse Pretorius","email":"jesse@odyssey4.me","username":"jesse-pretorius"},"change_message_id":"8dfcf84c82784b062a63d0e7512460bf137566c0","unresolved":false,"context_lines":[{"line_number":17,"context_line":"currently considered fully ready for production deployments either."},{"line_number":18,"context_line":""},{"line_number":19,"context_line":"Once stable-3.2 has seen a few point releases, it should be safe to"},{"line_number":20,"context_line":"move to that branch."},{"line_number":21,"context_line":""},{"line_number":22,"context_line":"Change-Id: Ibd8f64d9889009cf6e80b92254fd580ff559b1be"},{"line_number":23,"context_line":"Related-Bug: 1802195"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":1,"id":"3f79a3b5_af63ad44","line":20,"updated":"2018-11-08 11:41:43.000000000","message":"I think we can safely use stable-3.2 on master for now. It\u0027s several months before we release Stein and we should be helping ceph-ansible test this RC.\n\nAlso, we\u0027ve done things in our master branch to accommodate their changes already - so if we want to go back to tracking 3.1, we\u0027ll likely have to undo a bunch of things we did.","commit_id":"c3ceeb83972e1b8ccf3dd00d071e4a89b705ea25"}]}