)]}'
{"doc/source/release-management.rst":[{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"0c1ab9309fa862f61d759bcef1bc18b06b12fb11","unresolved":false,"context_lines":[{"line_number":9,"context_line":"use git tags to define the release points."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"OpenStack deliverables can be released under various models. They all follow"},{"line_number":12,"context_line":"the common 6-month development cycle, but may release more than once during"},{"line_number":13,"context_line":"those cycles. The release management team manages the release process for"},{"line_number":14,"context_line":"a selection of project teams repositories (indicated by the release:managed"},{"line_number":15,"context_line":"tag) and provide tools for other teams and repositories to do self-service"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_3351770f","line":12,"updated":"2015-06-19 13:29:40.000000000","message":"Is this true with release-independent being a valid tag now? For instance, client and libraries are released in their own windows. I think the wording here should be changed to accurately reflect the fact we\u0027re tagging about those projects with the tag \"integrated-release\" or some such thing.","commit_id":"4961f56991f8d3ae65376144861879413e60c360"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"1795ab1865a948d7d01d7a30163ca768f200d984","unresolved":false,"context_lines":[{"line_number":9,"context_line":"use git tags to define the release points."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"OpenStack deliverables can be released under various models. They all follow"},{"line_number":12,"context_line":"the common 6-month development cycle, but may release more than once during"},{"line_number":13,"context_line":"those cycles. The release management team manages the release process for"},{"line_number":14,"context_line":"a selection of project teams repositories (indicated by the release:managed"},{"line_number":15,"context_line":"tag) and provide tools for other teams and repositories to do self-service"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_b3aca736","line":12,"in_reply_to":"fa32b979_3351770f","updated":"2015-06-19 13:43:44.000000000","message":"It is still true of release:independent projects. They still operate on a 6-month development cycle, they still make \"liberty releases\". They no longer do \"6-month time-based releases\" but that\u0027s a different thing. The cycle is just a 6-month series of releases branded under a common name. This is important especially since they will have a single release (the final one) with stable branches.","commit_id":"4961f56991f8d3ae65376144861879413e60c360"},{"author":{"_account_id":105,"name":"Kyle Mestery","email":"mestery@mestery.com","username":"mestery"},"change_message_id":"dba5f38b4715bb9d26ad504900477fe309ab9f03","unresolved":false,"context_lines":[{"line_number":9,"context_line":"use git tags to define the release points."},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"OpenStack deliverables can be released under various models. They all follow"},{"line_number":12,"context_line":"the common 6-month development cycle, but may release more than once during"},{"line_number":13,"context_line":"those cycles. The release management team manages the release process for"},{"line_number":14,"context_line":"a selection of project teams repositories (indicated by the release:managed"},{"line_number":15,"context_line":"tag) and provide tools for other teams and repositories to do self-service"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_b32107b7","line":12,"in_reply_to":"fa32b979_b3aca736","updated":"2015-06-19 13:45:08.000000000","message":"OK, this makes sense to me. Thanks for the clarification!","commit_id":"4961f56991f8d3ae65376144861879413e60c360"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"5f2eefff37606b074b0b92d48a94270c0e56d61f","unresolved":false,"context_lines":[{"line_number":16,"context_line":"releases."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Common time-based release model"},{"line_number":19,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"By default, most OpenStack services opt to follow the common, time-based"},{"line_number":22,"context_line":"release model. It is recommended at the earlier stages of development, when"}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_844a74ab","line":19,"updated":"2015-06-19 15:43:51.000000000","message":"We might want some subheadings in this section, to make it possible to link directly to information like the backport and feature freeze paragraphs. We can think about that as a second patch, though.","commit_id":"4961f56991f8d3ae65376144861879413e60c360"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"5f2eefff37606b074b0b92d48a94270c0e56d61f","unresolved":false,"context_lines":[{"line_number":92,"context_line":"version, and the master branch will from then on produce releases of the"},{"line_number":93,"context_line":"new development cycle. If a critical issue is found in the \"final release\","},{"line_number":94,"context_line":"backports can be pushed to the stable branch and a new \"final release\" be"},{"line_number":95,"context_line":"tagged there. That is why it is important to switch the Y component of the"},{"line_number":96,"context_line":"X.Y.Z version when we switch to the next development cycle, so that the Z"},{"line_number":97,"context_line":"component can be used in future tags on the stable branch."},{"line_number":98,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fa32b979_e46b40f0","line":95,"updated":"2015-06-19 15:43:51.000000000","message":"We need to increment *at least* the Y component. We could also raise the major version, if that is appropriate.","commit_id":"4961f56991f8d3ae65376144861879413e60c360"}]}