)]}'
{"deliverables/rocky/tosca-parser.yaml":[{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"3b776f4e4a1c3b4175c14a23940adb7fc13dcff1","unresolved":false,"context_lines":[{"line_number":9,"context_line":"      - hash: e17c2a8060434a27293cd4719647cf735216f3c0"},{"line_number":10,"context_line":"        repo: openstack/tosca-parser"},{"line_number":11,"context_line":"    version: 1.0.0"},{"line_number":12,"context_line":"branches:"},{"line_number":13,"context_line":"  - location: 1.0.0"},{"line_number":14,"context_line":"    name: stable/rocky"},{"line_number":15,"context_line":"repository-settings:"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"5f7c97a3_96e30106","line":12,"updated":"2018-05-05 13:46:13.000000000","message":"This will create a new branch. It\u0027s *very* early in the cycle to do that, since it will mean you have to backport all changes from master to that branch to release them as part of future rocky updates. Is that what you really want to do? If not, you can just tag on master until the end of the cycle by leaving the \"branches\" section out of this file, and then we can create the maintenance branch at the end of the cycle like we normally do.","commit_id":"bbf0a8cfce9f9e86950fd5a4f0b82b75e16ae55b"}]}