)]}'
{"reference/projects.yaml":[{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"c618a61083ba19d5cf4340ef4eccde27da252469","unresolved":false,"context_lines":[{"line_number":130,"context_line":"        - assert:supports-upgrade"},{"line_number":131,"context_line":"        - stable:follows-policy"},{"line_number":132,"context_line":"        - assert:supports-rolling-upgrade"},{"line_number":133,"context_line":"        - docs:follows-policy"},{"line_number":134,"context_line":"    cinder-specs:"},{"line_number":135,"context_line":"      repos:"},{"line_number":136,"context_line":"        - openstack/cinder-specs"}],"source_content_type":"text/x-yaml","patch_set":28,"id":"bff0334d_a66d8433","line":133,"updated":"2017-04-07 18:12:56.000000000","message":"We will need to get the PTLs of these teams to sign off on adding the tag, otherwise we\u0027re asserting an agreement they haven\u0027t made. It might be better to leave the application of the tag to a separate patch (or set of patches).","commit_id":"011d4ec8e5ea9c635290ed2f2ef7e377e61fbbd8"}],"reference/tags/doc-approved-tag.rst":[{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"e55f2f472076bb224011bb05dc15a63d8629ed62","unresolved":false,"context_lines":[{"line_number":10,"context_line":"docs:install-guide-verified"},{"line_number":11,"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"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag certifies that the OpenStack manuals team and $project certify this"},{"line_number":14,"context_line":"guide as fully deployable. Specifically, the Installation Guide"},{"line_number":15,"context_line":"(at docs.openstack.org) has fully functional and verified instructions for"},{"line_number":16,"context_line":"specific projects. The tag has two elements:"},{"line_number":17,"context_line":"    "}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a1ff146_f313ba0b","line":14,"range":{"start_line":13,"start_character":9,"end_line":14,"end_character":25},"updated":"2017-03-14 15:37:12.000000000","message":"certify is too strong IMHO.","commit_id":"5dd5a41390c2812606097dd4fa9c9e9cf4fed0a6"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"e55f2f472076bb224011bb05dc15a63d8629ed62","unresolved":false,"context_lines":[{"line_number":14,"context_line":"guide as fully deployable. Specifically, the Installation Guide"},{"line_number":15,"context_line":"(at docs.openstack.org) has fully functional and verified instructions for"},{"line_number":16,"context_line":"specific projects. The tag has two elements:"},{"line_number":17,"context_line":"    "},{"line_number":18,"context_line":"- Verified: The documentation team has successfully worked alongside the"},{"line_number":19,"context_line":"            $project to ensure that the $project installs successfully, and all"},{"line_number":20,"context_line":"            major bugs and enhancements of the $release have been documented"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a1ff146_1372167d","line":17,"range":{"start_line":17,"start_character":0,"end_line":17,"end_character":4},"updated":"2017-03-14 15:37:12.000000000","message":"nit: Extra whitespace, also line 22","commit_id":"5dd5a41390c2812606097dd4fa9c9e9cf4fed0a6"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"e55f2f472076bb224011bb05dc15a63d8629ed62","unresolved":false,"context_lines":[{"line_number":81,"context_line":"     integrated into the documentation."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"  #. The project team is responsible for either:"},{"line_number":84,"context_line":"     "},{"line_number":85,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":86,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":87,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"}],"source_content_type":"text/x-rst","patch_set":1,"id":"3a1ff146_d3dcfe48","line":84,"range":{"start_line":84,"start_character":0,"end_line":84,"end_character":5},"updated":"2017-03-14 15:37:12.000000000","message":"nit: extra whitespace, aslo below line  97","commit_id":"5dd5a41390c2812606097dd4fa9c9e9cf4fed0a6"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"cad5306b735665282ad9bef813089b7bea4e8c95","unresolved":false,"context_lines":[{"line_number":53,"context_line":"OpenStack using the manuals. This is on the proviso that there is no issue with"},{"line_number":54,"context_line":"the distribution packages."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"This tag would be required for the base projects:"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* Horizon"},{"line_number":59,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a1ff146_137776d5","line":56,"range":{"start_line":56,"start_character":0,"end_line":56,"end_character":49},"updated":"2017-03-14 15:47:25.000000000","message":"What happens for the base projects that do not follow this?","commit_id":"c163642fe569f9cec324bf0dc43ec840a4fd09b3"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"ffeb9663078445798f980e4055a9d5edb6db9dae","unresolved":false,"context_lines":[{"line_number":53,"context_line":"OpenStack using the manuals. This is on the proviso that there is no issue with"},{"line_number":54,"context_line":"the distribution packages."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"This tag would be required for the base projects:"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* Horizon"},{"line_number":59,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a1ff146_9317e653","line":56,"range":{"start_line":56,"start_character":0,"end_line":56,"end_character":49},"in_reply_to":"3a1ff146_137776d5","updated":"2017-03-14 15:48:53.000000000","message":"As I said above (which, should I make clearer?) and below (I think it\u0027s clear enough there, but too late) they will receive a \"\"docs:install-guide-not-verified\".\n\nWhich might mean we need to make two tags?","commit_id":"c163642fe569f9cec324bf0dc43ec840a4fd09b3"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"27ad70d1224e542340c253447fcc032a94a2be0f","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":91,"context_line":"       action would also require at least one +1 from a member of the relevant"},{"line_number":92,"context_line":"       project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"* 4 weeks before release: The CPL has reviewed the documentation for their"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a1ff146_abc62a14","line":92,"updated":"2017-03-14 16:41:27.000000000","message":"I think seen as we trust these projects to write the initial content we should trust them to do this.\n\nAs long as the CPL does the testing later on, it should be OK","commit_id":"c163642fe569f9cec324bf0dc43ec840a4fd09b3"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"136ea21ad9d2fbde27c0121aa6e50b1d39e1d90f","unresolved":false,"context_lines":[{"line_number":89,"context_line":""},{"line_number":90,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":91,"context_line":"       action would also require at least one +1 from a member of the relevant"},{"line_number":92,"context_line":"       project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":93,"context_line":""},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"* 4 weeks before release: The CPL has reviewed the documentation for their"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3a1ff146_79732b4e","line":92,"range":{"start_line":92,"start_character":7,"end_line":92,"end_character":68},"updated":"2017-03-14 16:15:08.000000000","message":"Will probably need to write a third use case for project-specific guides that live in their own repo.\nDoes the doc team need to give at least a +1 (from the PTL?), or do we entrust the optional projects on their own?","commit_id":"c163642fe569f9cec324bf0dc43ec840a4fd09b3"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":4,"context_line":"  Unported License."},{"line_number":5,"context_line":"  http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":".. _`tag-\u003cdocs\u003e`:install-guide-verified"},{"line_number":8,"context_line":""},{"line_number":9,"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"},{"line_number":10,"context_line":"docs:install-guide-verified"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_33218fa0","line":7,"updated":"2017-03-15 21:36:06.000000000","message":".. _`tag-docs:install-guide-verified`:","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":7,"context_line":".. _`tag-\u003cdocs\u003e`:install-guide-verified"},{"line_number":8,"context_line":""},{"line_number":9,"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"},{"line_number":10,"context_line":"docs:install-guide-verified"},{"line_number":11,"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"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag certifies that the OpenStack manuals team and $project certify this"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_930fa32d","line":10,"updated":"2017-03-15 21:36:06.000000000","message":"The filename and the tag name should match.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"c94b7ec4f8c01304752414dd35158c2dc647834c","unresolved":false,"context_lines":[{"line_number":20,"context_line":"            major bugs and enhancements of the $release have been documented"},{"line_number":21,"context_line":"            sufficiently."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"- Not Verified: The documentation team has implemented any bug fixes and"},{"line_number":24,"context_line":"                enhancements they are aware of, but this project has not been tested"},{"line_number":25,"context_line":"                for full functionality and cannot guarantee deployment."},{"line_number":26,"context_line":"                No documentation exists."},{"line_number":27,"context_line":"                Suffers from major bugs that prevent it from being used to perform a"},{"line_number":28,"context_line":"                basic installation."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Application to current projects"},{"line_number":31,"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"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_33b45df1","line":28,"range":{"start_line":23,"start_character":0,"end_line":28,"end_character":35},"updated":"2017-03-15 02:36:21.000000000","message":"I don\u0027t think this is required.  Lack of the tag implies this.  Much like we do with the stable:follows-policy tag.  If  a project meets the criteria they get the tag otherwise it\u0027s just best effort but no promises are made.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"9f828afb42d0338c92b03ab5423055ae2a50092c","unresolved":false,"context_lines":[{"line_number":20,"context_line":"            major bugs and enhancements of the $release have been documented"},{"line_number":21,"context_line":"            sufficiently."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"- Not Verified: The documentation team has implemented any bug fixes and"},{"line_number":24,"context_line":"                enhancements they are aware of, but this project has not been tested"},{"line_number":25,"context_line":"                for full functionality and cannot guarantee deployment."},{"line_number":26,"context_line":"                No documentation exists."},{"line_number":27,"context_line":"                Suffers from major bugs that prevent it from being used to perform a"},{"line_number":28,"context_line":"                basic installation."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Application to current projects"},{"line_number":31,"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"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_431739a3","line":28,"range":{"start_line":23,"start_character":0,"end_line":28,"end_character":35},"in_reply_to":"3a1ff146_33b45df1","updated":"2017-03-15 11:34:12.000000000","message":"Okay. So keeping the criteria, we just have \u0027no\u0027 tag for unverified documentation.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":20,"context_line":"            major bugs and enhancements of the $release have been documented"},{"line_number":21,"context_line":"            sufficiently."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"- Not Verified: The documentation team has implemented any bug fixes and"},{"line_number":24,"context_line":"                enhancements they are aware of, but this project has not been tested"},{"line_number":25,"context_line":"                for full functionality and cannot guarantee deployment."},{"line_number":26,"context_line":"                No documentation exists."},{"line_number":27,"context_line":"                Suffers from major bugs that prevent it from being used to perform a"},{"line_number":28,"context_line":"                basic installation."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Application to current projects"},{"line_number":31,"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"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_b3357fdb","line":28,"range":{"start_line":23,"start_character":0,"end_line":28,"end_character":35},"in_reply_to":"3a1ff146_431739a3","updated":"2017-03-15 21:36:06.000000000","message":"We only need the affirmative tag.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Application to current projects"},{"line_number":31,"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":32,"context_line":""},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Rationale"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_f34d3773","line":32,"updated":"2017-03-15 21:36:06.000000000","message":"The template should have had some boilerplate to generate the content for this section automatically. Please reinsert that here.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":48,"context_line":"all necessary major bug fixes and enhancements. However, this method no longer"},{"line_number":49,"context_line":"ensures that the documentation is verified by the teams each release."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"Therefore, I propose that we introduce \"docs:install-guide-verified\" to"},{"line_number":52,"context_line":"ensure that, at the very least, a user is able to successfully deploy"},{"line_number":53,"context_line":"OpenStack using the manuals. This is on the proviso that there is no issue with"},{"line_number":54,"context_line":"the distribution packages."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_1351f30e","line":51,"updated":"2017-03-15 21:36:06.000000000","message":"There\u0027s no need to \"propose\" the tag in the body of the tag description. The patch is the proposal. :-)\n\nThis paragraph can be rewritten assuming that the tag is approved, because if it isn\u0027t the patch won\u0027t land.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":53,"context_line":"OpenStack using the manuals. This is on the proviso that there is no issue with"},{"line_number":54,"context_line":"the distribution packages."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"This tag would be required for the base projects:"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* Horizon"},{"line_number":59,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_f374579d","line":56,"updated":"2017-03-15 21:36:06.000000000","message":"We do not currently require tags for any projects, so this is a new precedent. Do we need to require it? Are those projects unlikely to want to sign up for the new tag? If so, does that indicate a need to negotiate the terms differently?","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"b5b75ca796008244dce415a402a40faad3d9dcae","unresolved":false,"context_lines":[{"line_number":53,"context_line":"OpenStack using the manuals. This is on the proviso that there is no issue with"},{"line_number":54,"context_line":"the distribution packages."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"This tag would be required for the base projects:"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* Horizon"},{"line_number":59,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a1ced50_12a3f29f","line":56,"in_reply_to":"3a1ff146_2f73d081","updated":"2017-03-16 18:06:10.000000000","message":"It sounds like the tag isn\u0027t so much \"required\" then but that those teams are \"grandfathered in\"?","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"94a278402f9a8c7363d6379903f341b6f8c87ae1","unresolved":false,"context_lines":[{"line_number":53,"context_line":"OpenStack using the manuals. This is on the proviso that there is no issue with"},{"line_number":54,"context_line":"the distribution packages."},{"line_number":55,"context_line":""},{"line_number":56,"context_line":"This tag would be required for the base projects:"},{"line_number":57,"context_line":""},{"line_number":58,"context_line":"* Horizon"},{"line_number":59,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_2f73d081","line":56,"in_reply_to":"3a1ff146_f374579d","updated":"2017-03-16 11:34:53.000000000","message":"So, it would be different, yes. As the \u0027base\u0027 projects, the documentation for the install guide still lives in the openstack-manauals tree, as opposed to the optional projects that live in their own trees and are built into the guide.\nThis is so, at the very least, at all times there are base install documentation being built from one repo.\n\nSo, my point here is more that I want to ensure that these projects are highlighted case points because it\u0027s not living in their tree. Does that make sense?\n\nTerms might need to be negotiated, yep.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":62,"context_line":"* Neutron"},{"line_number":63,"context_line":"* Cinder"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"The tag would be required for the optional projects that currently"},{"line_number":66,"context_line":"maintain a project-specific Installation Guide linked to the"},{"line_number":67,"context_line":"docs.openstack.org page"},{"line_number":68,"context_line":"`https://docs.openstack.org/project-install-guide/ocata/ubuntu-services.html`_"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_53a9abde","line":65,"updated":"2017-03-15 21:36:06.000000000","message":"Again, rephrase this assuming the tag description is approved.\n\n\"Projects that maintain project-specific Installation Guides must have this tag for their guide to be linked from docs.openstack.org.\"","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":73,"context_line":"A project that receives the \"docs:install-guide-verified\" tag should, at a minimum,"},{"line_number":74,"context_line":"meet the following requirements:"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* 6 weeks before release: The CPL has made the docs team aware of all major new"},{"line_number":77,"context_line":"  features and bug fixes up till this point."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"  #. The documentation release team maintains an action item list of all"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_53ce0bb5","line":76,"range":{"start_line":76,"start_character":30,"end_line":76,"end_character":33},"updated":"2017-03-15 21:36:06.000000000","message":"What is a \"CPL\"?","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"94a278402f9a8c7363d6379903f341b6f8c87ae1","unresolved":false,"context_lines":[{"line_number":73,"context_line":"A project that receives the \"docs:install-guide-verified\" tag should, at a minimum,"},{"line_number":74,"context_line":"meet the following requirements:"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* 6 weeks before release: The CPL has made the docs team aware of all major new"},{"line_number":77,"context_line":"  features and bug fixes up till this point."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"  #. The documentation release team maintains an action item list of all"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_8f684489","line":76,"range":{"start_line":76,"start_character":30,"end_line":76,"end_character":33},"in_reply_to":"3a1ff146_53ce0bb5","updated":"2017-03-16 11:34:53.000000000","message":"Cross project liaison, I\u0027ll update :)","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"b5b75ca796008244dce415a402a40faad3d9dcae","unresolved":false,"context_lines":[{"line_number":73,"context_line":"A project that receives the \"docs:install-guide-verified\" tag should, at a minimum,"},{"line_number":74,"context_line":"meet the following requirements:"},{"line_number":75,"context_line":""},{"line_number":76,"context_line":"* 6 weeks before release: The CPL has made the docs team aware of all major new"},{"line_number":77,"context_line":"  features and bug fixes up till this point."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"  #. The documentation release team maintains an action item list of all"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a1ced50_52ad6a87","line":76,"range":{"start_line":76,"start_character":30,"end_line":76,"end_character":33},"in_reply_to":"3a1ff146_8f684489","updated":"2017-03-16 18:06:10.000000000","message":"We have many cross project liaisons for different purposes. I assume you mean the documentation liaison here.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":78,"context_line":""},{"line_number":79,"context_line":"  #. The documentation release team maintains an action item list of all"},{"line_number":80,"context_line":"     new major bugs and new enhancements that have not already been"},{"line_number":81,"context_line":"     integrated into the documentation."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"  #. The project team is responsible for either:"},{"line_number":84,"context_line":""}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_13d49345","line":81,"updated":"2017-03-15 21:36:06.000000000","message":"It feels a bit odd to encode process information from one team in the list of requirements being placed on another. Is this bullet point needed? Maybe a description can go in the rationale section as part of the doc team\u0027s side of the \"contract\" and then the requirements list can be just the things expected of teams who want the tag.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":93,"context_line":""},{"line_number":94,"context_line":""},{"line_number":95,"context_line":"* 4 weeks before release: The CPL has reviewed the documentation for their"},{"line_number":96,"context_line":"  team project, and either:"},{"line_number":97,"context_line":""},{"line_number":98,"context_line":"  #. Provided sufficient information to the documentation team in a bug report to"},{"line_number":99,"context_line":"     ensure the bug or enhancement is documented appropriately. This action"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_535c4bed","line":96,"updated":"2017-03-15 21:36:06.000000000","message":"Both this entry and the previous one describe an action that will happen in the future. Or that has happened in the past, maybe? Are teams going to apply for this tag before they have done this work, or after?\n\nMaybe this should be \"Project team agrees to ensure that the CPL has reviewed the documentation for the team project at least 4 weeks before the release, and either:\".","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":111,"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"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Proposals to add the tag must be reviewed 4 weeks before the end of the"},{"line_number":114,"context_line":"cycle to coincide with the project team review period."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"The tag is tentatively added provided the project is on track to release"},{"line_number":117,"context_line":"sufficient documentation, or the tag is removed and replaced with"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_1330139e","line":114,"updated":"2017-03-15 21:36:06.000000000","message":"Do you want to hard-code durations in this document? Or name the deadlines and then set the dates on the release schedule each cycle?","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"b5b75ca796008244dce415a402a40faad3d9dcae","unresolved":false,"context_lines":[{"line_number":111,"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"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Proposals to add the tag must be reviewed 4 weeks before the end of the"},{"line_number":114,"context_line":"cycle to coincide with the project team review period."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"The tag is tentatively added provided the project is on track to release"},{"line_number":117,"context_line":"sufficient documentation, or the tag is removed and replaced with"}],"source_content_type":"text/x-rst","patch_set":3,"id":"1a1ced50_32c70e47","line":114,"in_reply_to":"3a1ff146_0f2a942c","updated":"2017-03-16 18:06:10.000000000","message":"If you just say something like \"the deadline specified on the release schedule\" then we can manage the dates easily on the releases repo where you don\u0027t need TC sign-off on changes.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"94a278402f9a8c7363d6379903f341b6f8c87ae1","unresolved":false,"context_lines":[{"line_number":111,"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"},{"line_number":112,"context_line":""},{"line_number":113,"context_line":"Proposals to add the tag must be reviewed 4 weeks before the end of the"},{"line_number":114,"context_line":"cycle to coincide with the project team review period."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"The tag is tentatively added provided the project is on track to release"},{"line_number":117,"context_line":"sufficient documentation, or the tag is removed and replaced with"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_0f2a942c","line":114,"in_reply_to":"3a1ff146_1330139e","updated":"2017-03-16 11:34:53.000000000","message":"Now I think about it, we probably want to set the dates on the release schedule. What do you recommend?","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"c94b7ec4f8c01304752414dd35158c2dc647834c","unresolved":false,"context_lines":[{"line_number":114,"context_line":"cycle to coincide with the project team review period."},{"line_number":115,"context_line":""},{"line_number":116,"context_line":"The tag is tentatively added provided the project is on track to release"},{"line_number":117,"context_line":"sufficient documentation, or the tag is removed and replaced with"},{"line_number":118,"context_line":"\"docs:install-guide-not-verified\"."},{"line_number":119,"context_line":""},{"line_number":120,"context_line":"Deprecation"},{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_b3492dd3","line":118,"range":{"start_line":117,"start_character":47,"end_line":118,"end_character":34},"updated":"2017-03-15 02:36:21.000000000","message":"As above, just removing docs:install-guide-verified should be enough.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"c94b7ec4f8c01304752414dd35158c2dc647834c","unresolved":false,"context_lines":[{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The doc tag would not have a deprecation period, but the tag will be temporarily"},{"line_number":124,"context_line":"removed during the lsat 6 weeks of release during review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_b3e5ada9","line":124,"range":{"start_line":124,"start_character":24,"end_line":124,"end_character":31},"updated":"2017-03-15 02:36:21.000000000","message":"It might make sense to remove it earlier in the cycle and only add it around R-4 assuming each project looks like they\u0027re going to achieve it.  but that\u0027s up to you and the TC to determine.\n\nIf we\u0027re going to to this I wonder if that suggests we shoudl tag the governance repo at the release time to it\u0027s trivial to answer the question \"Did glance have the doc:install-guide-verified tag for the pike release\" after the fact.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"c94b7ec4f8c01304752414dd35158c2dc647834c","unresolved":false,"context_lines":[{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The doc tag would not have a deprecation period, but the tag will be temporarily"},{"line_number":124,"context_line":"removed during the lsat 6 weeks of release during review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_f311e5b0","line":124,"range":{"start_line":124,"start_character":19,"end_line":124,"end_character":23},"updated":"2017-03-15 02:36:21.000000000","message":"last","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"66a9116a3431d56372baec12470d8a4fe582a6fd","unresolved":false,"context_lines":[{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The doc tag would not have a deprecation period, but the tag will be temporarily"},{"line_number":124,"context_line":"removed during the lsat 6 weeks of release during review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_d3c4bb60","line":124,"range":{"start_line":124,"start_character":24,"end_line":124,"end_character":31},"in_reply_to":"3a1ff146_835f7171","updated":"2017-03-15 21:36:06.000000000","message":"This is going to result in a lot of churn in the governance repository, and it won\u0027t be clear to a user whether the tag applies to any given set of manuals or not.\n\nCan we instead say that each team will be reviewed by the docs team after each cycle, and if there are issues then there would be a discussion and if the issues are not resolved then the tag will be removed? That way we only make tag changes that are actually needed.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"9f828afb42d0338c92b03ab5423055ae2a50092c","unresolved":false,"context_lines":[{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The doc tag would not have a deprecation period, but the tag will be temporarily"},{"line_number":124,"context_line":"removed during the lsat 6 weeks of release during review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_835f7171","line":124,"range":{"start_line":124,"start_character":24,"end_line":124,"end_character":31},"in_reply_to":"3a1ff146_b3e5ada9","updated":"2017-03-15 11:34:12.000000000","message":"That\u0027s a fair comment. Might be worth doing so. I guess I just don\u0027t want the tag to only hang around for a few weeks, when in reality, users are looking at the documentation the whole release and the idea is that our users know that the documentation has been confirmed. Thoughts?\n\nI am definitely misunderstanding, what does tagging the governance repo achieve here?","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"94a278402f9a8c7363d6379903f341b6f8c87ae1","unresolved":false,"context_lines":[{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The doc tag would not have a deprecation period, but the tag will be temporarily"},{"line_number":124,"context_line":"removed during the lsat 6 weeks of release during review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_8feda4f1","line":124,"range":{"start_line":124,"start_character":24,"end_line":124,"end_character":31},"in_reply_to":"3a1ff146_d3c4bb60","updated":"2017-03-16 11:34:53.000000000","message":"That works for me, I\u0027ll update with a summary as such.","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"9f828afb42d0338c92b03ab5423055ae2a50092c","unresolved":false,"context_lines":[{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"The doc tag would not have a deprecation period, but the tag will be temporarily"},{"line_number":124,"context_line":"removed during the lsat 6 weeks of release during review."}],"source_content_type":"text/x-rst","patch_set":3,"id":"3a1ff146_031e21ba","line":124,"range":{"start_line":124,"start_character":19,"end_line":124,"end_character":23},"in_reply_to":"3a1ff146_f311e5b0","updated":"2017-03-15 11:34:12.000000000","message":"I like it as lsat ;)","commit_id":"f551ac056a114e30d46016d28f46df524cbc9653"}],"reference/tags/docs-install-guide-verified.rst":[{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":8,"id":"1a1ced50_12d132fc","updated":"2017-03-16 18:21:12.000000000","message":"It looks like we\u0027re using a convention of naming files with an underscore replacing the colon after the scoping prefix. So this file should be docs_install-guide-verified.rst","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag confirms that the OpenStack manuals team and $PROJECT confirm this"},{"line_number":14,"context_line":"guide as fully deployable. Specifically, the Installation Guide"},{"line_number":15,"context_line":"(at docs.openstack.org) has fully functional and verified instructions for"},{"line_number":16,"context_line":"specific projects. This tag is defined as:"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"- Verified: The documentation team has successfully worked alongside the"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_32f54e83","line":15,"updated":"2017-03-16 18:21:12.000000000","message":"could this reference to the installation guide be a link? Or is that hard because it changes for each release series?","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"7999c0f4e1d8d1234aa42b71a4b60e13d71beeb5","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag confirms that the OpenStack manuals team and $PROJECT confirm this"},{"line_number":14,"context_line":"guide as fully deployable. Specifically, the Installation Guide"},{"line_number":15,"context_line":"(at docs.openstack.org) has fully functional and verified instructions for"},{"line_number":16,"context_line":"specific projects. This tag is defined as:"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"- Verified: The documentation team has successfully worked alongside the"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_a6f8d14a","line":15,"in_reply_to":"1a1ced50_32f54e83","updated":"2017-03-20 14:56:00.000000000","message":"I guess since we\u0027re applying this in Pike, I can link to the draft repo. That would essentially make sense, and then the link itself would never break.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":15,"context_line":"(at docs.openstack.org) has fully functional and verified instructions for"},{"line_number":16,"context_line":"specific projects. This tag is defined as:"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"- Verified: The documentation team has successfully worked alongside the"},{"line_number":19,"context_line":"            $PROJECT to ensure that the $PROJECT installs successfully, and all"},{"line_number":20,"context_line":"            major bugs and enhancements of the $RELEASE have been documented"},{"line_number":21,"context_line":"            sufficiently."}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_f239f642","line":18,"updated":"2017-03-16 18:21:12.000000000","message":"You can probably drop the \"- Verified:\" prefix here, since there\u0027s no negative tag any more.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":16,"context_line":"specific projects. This tag is defined as:"},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"- Verified: The documentation team has successfully worked alongside the"},{"line_number":19,"context_line":"            $PROJECT to ensure that the $PROJECT installs successfully, and all"},{"line_number":20,"context_line":"            major bugs and enhancements of the $RELEASE have been documented"},{"line_number":21,"context_line":"            sufficiently."},{"line_number":22,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_d2595a90","line":19,"updated":"2017-03-16 18:21:12.000000000","message":"we just use \"project\" instead of variable syntax since these docs are often read by folks not familiar with the $ convention.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":17,"context_line":""},{"line_number":18,"context_line":"- Verified: The documentation team has successfully worked alongside the"},{"line_number":19,"context_line":"            $PROJECT to ensure that the $PROJECT installs successfully, and all"},{"line_number":20,"context_line":"            major bugs and enhancements of the $RELEASE have been documented"},{"line_number":21,"context_line":"            sufficiently."},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"Application to current projects"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_1254d252","line":20,"updated":"2017-03-16 18:21:12.000000000","message":"ditto for $RELEASE","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":27,"context_line":"the proposed tag to at least some subset of the current project list. This"},{"line_number":28,"context_line":"will serve as an example of how the tag should be applied in the real world."},{"line_number":29,"context_line":"You may also submit (as a subsequent change) the corresponding governance"},{"line_number":30,"context_line":"change to immediately apply the proposed tag to projects."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":".. tagged-projects:: \u003ctag name\u003e"},{"line_number":33,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_92c60215","line":30,"updated":"2017-03-16 18:21:12.000000000","message":"You can drop this paragraph, they are instructions to the tag document author.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":29,"context_line":"You may also submit (as a subsequent change) the corresponding governance"},{"line_number":30,"context_line":"change to immediately apply the proposed tag to projects."},{"line_number":31,"context_line":""},{"line_number":32,"context_line":".. tagged-projects:: \u003ctag name\u003e"},{"line_number":33,"context_line":""},{"line_number":34,"context_line":"Rationale"},{"line_number":35,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_32d8eeef","line":32,"updated":"2017-03-16 18:21:12.000000000","message":"replace \u003ctag name\u003e with docs:install-guide-verified","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":37,"context_line":"At present, the documentation team is responsible for all documentation in the"},{"line_number":38,"context_line":"openstack/openstack-manuals repo. Maintaining this documentation requires base"},{"line_number":39,"context_line":"knowledge of at least the base projects, and occasionally, some of the"},{"line_number":40,"context_line":"optional projects."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"However, being able to successfully maintain some of the more in-depth"},{"line_number":43,"context_line":"knowledge that is written in the guides is often out of scope for the"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_5293aafa","line":40,"updated":"2017-03-16 18:21:12.000000000","message":"We don\u0027t really talk about \"base\" and \"optional\" projects anywhere else. You could talk about starter-kit services, maybe, since that\u0027s a classification we do have.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"7999c0f4e1d8d1234aa42b71a4b60e13d71beeb5","unresolved":false,"context_lines":[{"line_number":37,"context_line":"At present, the documentation team is responsible for all documentation in the"},{"line_number":38,"context_line":"openstack/openstack-manuals repo. Maintaining this documentation requires base"},{"line_number":39,"context_line":"knowledge of at least the base projects, and occasionally, some of the"},{"line_number":40,"context_line":"optional projects."},{"line_number":41,"context_line":""},{"line_number":42,"context_line":"However, being able to successfully maintain some of the more in-depth"},{"line_number":43,"context_line":"knowledge that is written in the guides is often out of scope for the"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_72276ab6","line":40,"in_reply_to":"1a1ced50_5293aafa","updated":"2017-03-20 14:56:00.000000000","message":"I recognise that this isn\u0027t referred to elsewhere, but that is what is detailed in the install guide. So, if you were to reference the docs.o.o page it distinctly identifies the projects with \u0027basic\u0027 or \u0027optional\u0027:\nhttps://docs.openstack.org/project-install-guide/draft/ubuntu-services.html\n\nI\u0027ll use \u0027starter-kit\u0027 but we might want to reference that?","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":48,"context_line":"all necessary major bug fixes and enhancements. However, this method no longer"},{"line_number":49,"context_line":"ensures that the documentation is verified by the teams each release."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"The \"docs:install-guide-verified\" is to ensure that, at the very least, a user"},{"line_number":52,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":53,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":54,"context_line":""}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_72a7c64f","line":51,"updated":"2017-03-16 18:21:12.000000000","message":"s/is/tag is/","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":52,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":53,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"This tag is required for the base projects:"},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* Horizon"},{"line_number":58,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_127772d5","line":55,"updated":"2017-03-16 18:21:12.000000000","message":"See my other comment on PS3 about using a term other than \"required\".","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* Glance"},{"line_number":60,"context_line":"* Nova"},{"line_number":61,"context_line":"* Neutron"},{"line_number":62,"context_line":"* Cinder"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Optional projects that maintain project-specific Installation Guides must have"},{"line_number":65,"context_line":"this tag for their guide to be linked from docs.openstack.org."}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_325b8e56","line":62,"updated":"2017-03-16 18:21:12.000000000","message":"It would make sense to edit projects.yaml to add the new tag to these projects as part of this patch, since they are all expected to have it anyway.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":61,"context_line":"* Neutron"},{"line_number":62,"context_line":"* Cinder"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Optional projects that maintain project-specific Installation Guides must have"},{"line_number":65,"context_line":"this tag for their guide to be linked from docs.openstack.org."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"The documentation release team maintains an action item list of all"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_9230c209","line":64,"updated":"2017-03-16 18:21:12.000000000","message":"s/Optional projects/Projects/","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":66,"context_line":""},{"line_number":67,"context_line":"The documentation release team maintains an action item list of all"},{"line_number":68,"context_line":"new major bugs and new enhancements that have not already been"},{"line_number":69,"context_line":"integrated into the documentation."},{"line_number":70,"context_line":""},{"line_number":71,"context_line":"Requirements"},{"line_number":72,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_9217e253","line":69,"updated":"2017-03-16 18:21:12.000000000","message":"How does this relate to the projects with or without the tag? Is the promise that the docs team will work on those items? Or just track them?","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":73,"context_line":""},{"line_number":74,"context_line":"To maintain the \"docs:install-guide-verified\" tag, the cross-project liaison (CPL)"},{"line_number":75,"context_line":"must have read the docs and opened appropriate bugs in docs by"},{"line_number":76,"context_line":"$INSTALL_GUIDE_DEADLINE, and provided information to the docs team on how to"},{"line_number":77,"context_line":"document these issues."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"The following structure is to be loosely followed, dependent on $PROJECT"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_f2165654","line":76,"updated":"2017-03-16 18:21:12.000000000","message":"s/$INSTALL_GUIDE_DEADLINE/the installation guide review deadline/","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":12807,"name":"Steve Lewis (stevelle)","email":"stevelle@gmail.com","username":"stevelle"},"change_message_id":"4ef6075cad182576bdd3fd5d0fa0c76dbecd1d1b","unresolved":false,"context_lines":[{"line_number":73,"context_line":""},{"line_number":74,"context_line":"To maintain the \"docs:install-guide-verified\" tag, the cross-project liaison (CPL)"},{"line_number":75,"context_line":"must have read the docs and opened appropriate bugs in docs by"},{"line_number":76,"context_line":"$INSTALL_GUIDE_DEADLINE, and provided information to the docs team on how to"},{"line_number":77,"context_line":"document these issues."},{"line_number":78,"context_line":""},{"line_number":79,"context_line":"The following structure is to be loosely followed, dependent on $PROJECT"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_a909b033","line":76,"range":{"start_line":76,"start_character":0,"end_line":76,"end_character":23},"updated":"2017-03-17 16:50:42.000000000","message":"when does this variable substitution happen?","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":79,"context_line":"The following structure is to be loosely followed, dependent on $PROJECT"},{"line_number":80,"context_line":"circumstance."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"* 6 weeks before release: The CPL has made the docs team"},{"line_number":83,"context_line":"  aware of all major new features and bug fixes up till this point."},{"line_number":84,"context_line":""},{"line_number":85,"context_line":"  #. The project team is responsible for either:"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_bd510f11","line":82,"updated":"2017-03-16 18:21:12.000000000","message":"s/CPL/liaison/","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":87,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":88,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":89,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":90,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":93,"context_line":"       action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_7d48775c","line":90,"updated":"2017-03-16 18:21:12.000000000","message":"If the review policy for these sorts of changes is documented elsewhere, you could refer directly to that to avoid having to come back here and change it if the docs team changes their processes.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"7999c0f4e1d8d1234aa42b71a4b60e13d71beeb5","unresolved":false,"context_lines":[{"line_number":87,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":88,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":89,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":90,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":93,"context_line":"       action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_929f86b3","line":90,"in_reply_to":"1a1ced50_7d48775c","updated":"2017-03-20 14:56:00.000000000","message":"It is not - I\u0027ll keep it documented here, and reference this, and document it in the contributor guide. I might push that up with the new patch.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":95,"context_line":""},{"line_number":96,"context_line":""},{"line_number":97,"context_line":"* Project team agrees to ensure that the CPL has reviewed the documentation for"},{"line_number":98,"context_line":"  the team project at least 4 weeks before the release, and either:"},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"  #. Provide sufficient information to the documentation team in a bug report to"},{"line_number":101,"context_line":"     ensure the bug or enhancement is documented appropriately. This action"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_1d6863ba","line":98,"updated":"2017-03-16 18:21:12.000000000","message":"another hard-coded deadline reference","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"c4b45100f247c8c2727c29dfb477ec80c04e497e","unresolved":false,"context_lines":[{"line_number":107,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":110,"context_line":"  to test installation instructions."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Tag application process"},{"line_number":113,"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"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3a1ff146_33a176a4","line":110,"updated":"2017-03-16 12:51:53.000000000","message":"Do we need to be explicit about the distros used for testing to be compliant with this? In other words, is testing with Ubuntu sufficient to say CentOS and SuSE are OK? Or are we expecting all supported distros to be validated before we can say this requirement has been met?","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"21765e45f21204ea3556b3166d8095ca8ad771d4","unresolved":false,"context_lines":[{"line_number":107,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":110,"context_line":"  to test installation instructions."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Tag application process"},{"line_number":113,"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"}],"source_content_type":"text/x-rst","patch_set":8,"id":"1a1ced50_bd866f63","line":110,"in_reply_to":"3a1ff146_19dadb78","updated":"2017-03-16 18:21:12.000000000","message":"Perhaps the thing to do is say that the instructions are tested for at least one distro, and the testing level of the other distros is documented clearly.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"6779294e08005a26146b5d8637952724bbfb3cf9","unresolved":false,"context_lines":[{"line_number":107,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":110,"context_line":"  to test installation instructions."},{"line_number":111,"context_line":""},{"line_number":112,"context_line":"Tag application process"},{"line_number":113,"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"}],"source_content_type":"text/x-rst","patch_set":8,"id":"3a1ff146_19dadb78","line":110,"in_reply_to":"3a1ff146_33a176a4","updated":"2017-03-16 13:40:57.000000000","message":"Good question. I think we should, at a very minimum, verify one of the three - the distro in question could be the preferred use case of the tester.\nThoughts? Or is this too generic? If so, perhaps then we define one and offer the other two as potentials.\nI admit asking the CPL to test all 3 distros is just way out of scope for most people.","commit_id":"faac15eac99de942b57a89e344876b81e2a2b328"}],"reference/tags/docs_follows-policy.rst":[{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"43ee7dd6501c75059da11ff0bc185edd5c351803","unresolved":false,"context_lines":[{"line_number":4,"context_line":"  Unported License."},{"line_number":5,"context_line":"  http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":".. _`tag-docs:follows-policy`:"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":10,"context_line":"docs:follows-policy"}],"source_content_type":"text/x-rst","patch_set":24,"id":"dfeb2761_e57c8e84","line":7,"range":{"start_line":7,"start_character":2,"end_line":7,"end_character":30},"updated":"2017-04-04 13:32:54.000000000","message":"This was at Thierry\u0027s suggestion, but I don\u0027t know if this is completely what we want to be saying. \n\nIt does solve the issue of it not being dependent on guides however.\n\nI\u0027d like some more doc-team input on this one. I admittedly cannot think of anything better right now, especially since I was originally advocating for the install-guide tag alone.","commit_id":"6cda172ce712276f0436fe396cc1c2bec2abd733"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4a7117cd6dbf54a7106265d2cbf2f5ad67514993","unresolved":false,"context_lines":[{"line_number":10,"context_line":"docs:follows-policy"},{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag is indicates that a deliverable’s documentation set is prepared in"},{"line_number":14,"context_line":"coordination with the OpenStack Documentation team following their defined"},{"line_number":15,"context_line":"practices and policies for review and verification. It does not indicate that"},{"line_number":16,"context_line":"the documentation team has taken ownership of producing the documentation for"}],"source_content_type":"text/x-rst","patch_set":26,"id":"bff0334d_7b5e51e7","line":13,"range":{"start_line":13,"start_character":9,"end_line":13,"end_character":11},"updated":"2017-04-05 20:02:26.000000000","message":"(strike)","commit_id":"991aee61ff095ad6a3c6baf649d4511fa43673f5"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"4a7117cd6dbf54a7106265d2cbf2f5ad67514993","unresolved":false,"context_lines":[{"line_number":35,"context_line":"ensures that the documentation is sufficiently verified by the teams each"},{"line_number":36,"context_line":"release."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":"The \"docs:follows-policy\" tag is used to ensure that project teams are"},{"line_number":39,"context_line":"coordinating with the documentation team, so that contributions, bug reports,"},{"line_number":40,"context_line":"and timely reviews happen over the course of each release cycle. Detailed"},{"line_number":41,"context_line":"expectations are described in the doc-tag section of the Documentation"}],"source_content_type":"text/x-rst","patch_set":26,"id":"bff0334d_3bc8c953","line":38,"range":{"start_line":38,"start_character":33,"end_line":38,"end_character":52},"updated":"2017-04-05 20:02:26.000000000","message":"Maybe we should say that the tag indicates this, rather than implying that it is somehow an enforcement mechanism.","commit_id":"991aee61ff095ad6a3c6baf649d4511fa43673f5"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":11,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag indicates that a deliverable’s documentation set is prepared in"},{"line_number":14,"context_line":"coordination with the OpenStack Documentation team following their defined"},{"line_number":15,"context_line":"practices and policies for review and verification. It does not indicate that"},{"line_number":16,"context_line":"the documentation team has taken ownership of producing the documentation for"},{"line_number":17,"context_line":"the deliverable."}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_18c6f249","line":14,"range":{"start_line":14,"start_character":46,"end_line":14,"end_character":60},"updated":"2017-04-07 00:13:47.000000000","message":"team, and follows","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":25,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"At present, the documentation team is responsible for all documentation in the"},{"line_number":28,"context_line":"openstack/openstack-manuals repo. Maintaining this documentation requires base"},{"line_number":29,"context_line":"knowledge of all of the projects covered by the guides. However, being able to"},{"line_number":30,"context_line":"successfully maintain some of the more in-depth knowledge that is written in the"},{"line_number":31,"context_line":"guides is out of scope for the technical writers to handle on their own."}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_b8e026ce","line":28,"range":{"start_line":28,"start_character":0,"end_line":28,"end_character":32},"updated":"2017-04-07 00:13:47.000000000","message":"add a link?","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":25,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"At present, the documentation team is responsible for all documentation in the"},{"line_number":28,"context_line":"openstack/openstack-manuals repo. Maintaining this documentation requires base"},{"line_number":29,"context_line":"knowledge of all of the projects covered by the guides. However, being able to"},{"line_number":30,"context_line":"successfully maintain some of the more in-depth knowledge that is written in the"},{"line_number":31,"context_line":"guides is out of scope for the technical writers to handle on their own."}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_58d11afb","line":28,"range":{"start_line":28,"start_character":74,"end_line":28,"end_character":78},"updated":"2017-04-07 00:13:47.000000000","message":"basic","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":45,"context_line":"project-specific guides inside of the openstack-manuals repository (such as,"},{"line_number":46,"context_line":"nova, neutron, cinder, horizon, glance, and keystone), including teams"},{"line_number":47,"context_line":"maintaining projects outside of the starter-kit set, and deployment projects,"},{"line_number":48,"context_line":"to apply for this tag. Having the tag indicates that the project teams commit"},{"line_number":49,"context_line":"to provide acurate documentation every release. In these cases, the"},{"line_number":50,"context_line":"documentation team will review the project team\u0027s guides, but won\u0027t"},{"line_number":51,"context_line":"necessarily contribute significanly to ongoing maintenance."}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_f8c46e61","line":48,"range":{"start_line":48,"start_character":0,"end_line":48,"end_character":8},"updated":"2017-04-07 00:13:47.000000000","message":"s/to apply/apply","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":46,"context_line":"nova, neutron, cinder, horizon, glance, and keystone), including teams"},{"line_number":47,"context_line":"maintaining projects outside of the starter-kit set, and deployment projects,"},{"line_number":48,"context_line":"to apply for this tag. Having the tag indicates that the project teams commit"},{"line_number":49,"context_line":"to provide acurate documentation every release. In these cases, the"},{"line_number":50,"context_line":"documentation team will review the project team\u0027s guides, but won\u0027t"},{"line_number":51,"context_line":"necessarily contribute significanly to ongoing maintenance."},{"line_number":52,"context_line":""}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_d8a1aaab","line":49,"range":{"start_line":49,"start_character":11,"end_line":49,"end_character":18},"updated":"2017-04-07 00:13:47.000000000","message":"accurate","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":60,"context_line":"For all teams:"},{"line_number":61,"context_line":""},{"line_number":62,"context_line":"1. The team must designate a liaison to the documentation team."},{"line_number":63,"context_line":"* https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"For project teams with deliverables, covered by the guides, that are maintained"},{"line_number":66,"context_line":"by the documentation team:"}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_78edfe89","line":63,"range":{"start_line":63,"start_character":0,"end_line":63,"end_character":68},"updated":"2017-04-07 00:13:47.000000000","message":"Indent the bullet point and put an empty line between it and the numbered point.\n\nOr add the link inline:\n\n1. The team must `designate a liaison \u003chttps://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation\u003e`_ to the documentation team.","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":62,"context_line":"1. The team must designate a liaison to the documentation team."},{"line_number":63,"context_line":"* https://wiki.openstack.org/wiki/CrossProjectLiaisons#Documentation"},{"line_number":64,"context_line":""},{"line_number":65,"context_line":"For project teams with deliverables, covered by the guides, that are maintained"},{"line_number":66,"context_line":"by the documentation team:"},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"1. The project team must provide summaries of new features, configuration changes,"},{"line_number":69,"context_line":"   etc. that need to be reflected in the documentation."}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_78a29e4d","line":66,"range":{"start_line":65,"start_character":0,"end_line":66,"end_character":26},"updated":"2017-04-07 00:13:47.000000000","message":"Remove the commas:\n\nFor project teams with deliverables covered by guides that are maintained by the documentation team:","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"1. The project team must provide summaries of new features, configuration changes,"},{"line_number":69,"context_line":"   etc. that need to be reflected in the documentation."},{"line_number":70,"context_line":"2. The documentation liaison must follow the published review schedule, and read"},{"line_number":71,"context_line":"   the documentation and open any appropriate bugs, either providing information"},{"line_number":72,"context_line":"   to the docs team on how to document these issues or submitting patches to fix them."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"For project teams with deliverables covered by documentation that is not maintained"}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_58b23a96","line":71,"range":{"start_line":70,"start_character":34,"end_line":71,"end_character":51},"updated":"2017-04-07 00:13:47.000000000","message":"follow the published review schedule, read the documentation, and open bugs appropriately,","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"5a22913aa8fecde15a854d639f1ef3e10bce7d23","unresolved":false,"context_lines":[{"line_number":75,"context_line":"by the documentation team:"},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"1. The project team must prepare their documentation using the standard tool set"},{"line_number":78,"context_line":"   provided by the documentation team, and ensure the guides are published to docs.openstack.org,"},{"line_number":79,"context_line":"   along with the guides for other official projects."},{"line_number":80,"context_line":"2. The project team must prepare and update their documentation following"},{"line_number":81,"context_line":"   the published review schedule, and coordinate with the documentation team"}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_ae2220a3","line":78,"range":{"start_line":78,"start_character":50,"end_line":78,"end_character":60},"updated":"2017-04-07 00:59:57.000000000","message":"This spec uses the phrase \"the guides\" a lot but does not define the list required to obtain this tag.  The spec should have the list of \"guides\".","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":76,"context_line":""},{"line_number":77,"context_line":"1. The project team must prepare their documentation using the standard tool set"},{"line_number":78,"context_line":"   provided by the documentation team, and ensure the guides are published to docs.openstack.org,"},{"line_number":79,"context_line":"   along with the guides for other official projects."},{"line_number":80,"context_line":"2. The project team must prepare and update their documentation following"},{"line_number":81,"context_line":"   the published review schedule, and coordinate with the documentation team"},{"line_number":82,"context_line":"   to ensure that a review is performed."}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_d84c0aa0","line":79,"range":{"start_line":79,"start_character":3,"end_line":79,"end_character":52},"updated":"2017-04-07 00:13:47.000000000","message":"Delete: along with the guides for other official projects\n\nIt makes it sound like the project team is responsible for publishing the guides for other projects.","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":93,"context_line":"Members of project teams who want the tag associated with their deliverables"},{"line_number":94,"context_line":"should apply for it by adding it to the deliverables they want to cover."},{"line_number":95,"context_line":""},{"line_number":96,"context_line":"The documentation team PTL must approve the tag to show that the documentation"},{"line_number":97,"context_line":"team agrees that the relevant guide(s) have been reviewed appropriately and"},{"line_number":98,"context_line":"follow the review deadlines related to this tag for each cycle."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"The tag is applied to deliverables in the governance repository. Each manual"},{"line_number":101,"context_line":"for a deliverable, covered by the tag, will be annotated to indicate the level"}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_d302ab09","line":98,"range":{"start_line":96,"start_character":0,"end_line":98,"end_character":63},"updated":"2017-04-07 00:13:47.000000000","message":"The wording makes it ambiguous as to who/what follows the review deadlines. Is it the guide or the PTL?\n\nRephrase:\n\nagrees that the relevant guides have been reviewed appropriately by the review deadline for each cycle as indicated by this tag.","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":12686,"name":"Brian Moss","email":"kallimachos@gmail.com","username":"bmoss"},"change_message_id":"07f847eda79140380c65a9f872f85b091da89ac6","unresolved":false,"context_lines":[{"line_number":97,"context_line":"team agrees that the relevant guide(s) have been reviewed appropriately and"},{"line_number":98,"context_line":"follow the review deadlines related to this tag for each cycle."},{"line_number":99,"context_line":""},{"line_number":100,"context_line":"The tag is applied to deliverables in the governance repository. Each manual"},{"line_number":101,"context_line":"for a deliverable, covered by the tag, will be annotated to indicate the level"},{"line_number":102,"context_line":"of input or review from the documentation team, so that users can easily"},{"line_number":103,"context_line":"discover who is responsible for maintining the content."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"Deprecation"},{"line_number":106,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":27,"id":"bff0334d_932543ae","line":103,"range":{"start_line":100,"start_character":65,"end_line":103,"end_character":55},"updated":"2017-04-07 00:13:47.000000000","message":"remove commas","commit_id":"f9adba0cb7cea806bb8de6b03695bdcc481dad3b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"8c1b7b19659a9ce04370ed9d74df9679f56e27c1","unresolved":false,"context_lines":[{"line_number":44,"context_line":"The documentation team recommends that project teams who maintain"},{"line_number":45,"context_line":"project-specific guides inside of the openstack-manuals repository (such as,"},{"line_number":46,"context_line":"nova, neutron, cinder, horizon, glance, and keystone), including teams"},{"line_number":47,"context_line":"maintaining projects outside of the starter-kit set, and deployment projects,"},{"line_number":48,"context_line":"apply for this tag. Having the tag indicates that the project teams commit"},{"line_number":49,"context_line":"to provide accurate documentation every release. In these cases, the"},{"line_number":50,"context_line":"documentation team will review the project team\u0027s guides, but won\u0027t"}],"source_content_type":"text/x-rst","patch_set":28,"id":"bff0334d_25670ac0","line":47,"range":{"start_line":47,"start_character":36,"end_line":47,"end_character":47},"updated":"2017-04-10 10:06:28.000000000","message":"You mean starter-kit:compute ?","commit_id":"011d4ec8e5ea9c635290ed2f2ef7e377e61fbbd8"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"957a27093c15e8cc1316f9f2340e66cfaf389858","unresolved":false,"context_lines":[{"line_number":19,"context_line":"Application to current projects"},{"line_number":20,"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":21,"context_line":""},{"line_number":22,"context_line":".. tagged-projects:: docs:follows-policy"},{"line_number":23,"context_line":""},{"line_number":24,"context_line":"Rationale"},{"line_number":25,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":30,"id":"7ffa3b31_a9fe7d34","line":22,"range":{"start_line":22,"start_character":21,"end_line":22,"end_character":40},"updated":"2017-04-18 20:05:12.000000000","message":"this name is just so meaningless to me, I really prefered the install guide verified approach.","commit_id":"6ea6c229c9b6d8e78694f3aaf7b5d0a9d8f87856"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ef0c444101eab101dff09d03d051a5910c908bfd","unresolved":false,"context_lines":[{"line_number":48,"context_line":"apply for this tag. Having the tag indicates that the project teams commit"},{"line_number":49,"context_line":"to provide accurate documentation every release. In these cases, the"},{"line_number":50,"context_line":"documentation team will review the project team\u0027s guides, but won\u0027t"},{"line_number":51,"context_line":"necessarily contribute significanly to ongoing maintenance."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Requirements"},{"line_number":54,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":30,"id":"7ffa3b31_d7cbd150","line":51,"range":{"start_line":51,"start_character":23,"end_line":51,"end_character":35},"updated":"2017-04-17 15:14:00.000000000","message":"nit, if you have to push another patch set: \u0027significantly\u0027","commit_id":"6ea6c229c9b6d8e78694f3aaf7b5d0a9d8f87856"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"f57ae04f783c651d1292990fc8f92e49b9587562","unresolved":false,"context_lines":[{"line_number":48,"context_line":"apply for this tag. Having the tag indicates that the project teams commit"},{"line_number":49,"context_line":"to provide accurate documentation every release. In these cases, the"},{"line_number":50,"context_line":"documentation team will review the project team\u0027s guides, but won\u0027t"},{"line_number":51,"context_line":"necessarily contribute significanly to ongoing maintenance."},{"line_number":52,"context_line":""},{"line_number":53,"context_line":"Requirements"},{"line_number":54,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":30,"id":"7ffa3b31_d97bffbb","line":51,"range":{"start_line":51,"start_character":23,"end_line":51,"end_character":35},"in_reply_to":"7ffa3b31_d7cbd150","updated":"2017-04-17 21:07:11.000000000","message":"Fixed in https://review.openstack.org/457358 so we don\u0027t need to recast votes on this patch.","commit_id":"6ea6c229c9b6d8e78694f3aaf7b5d0a9d8f87856"}],"reference/tags/docs_install-guide-verified.rst":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5f9dc44b09433ff3b37190a4532a6df2475692c6","unresolved":false,"context_lines":[{"line_number":10,"context_line":"docs:install-guide-verified"},{"line_number":11,"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"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag confirms that the OpenStack manuals team and project confirm this"},{"line_number":14,"context_line":"guide as fully deployable. Specifically, the"},{"line_number":15,"context_line":"`Installation Guide \u003chttps://docs.openstack.org/project-install-guide/draft/\u003e`_"},{"line_number":16,"context_line":"has fully functional and verified instructions for"},{"line_number":17,"context_line":"specific projects. This tag is defined as:"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_156f0093","line":14,"range":{"start_line":13,"start_character":62,"end_line":14,"end_character":25},"updated":"2017-03-20 15:21:10.000000000","message":"This is a bit imprecise since we\u0027re talking about the instructions actually working, not the guide itself being deployable.  Is there something you want to convey that wouldn\u0027t be expressed by combining these two sentences into:\n\nThis tag expresses that the OpenStack manuals team and the project asserting the tag verify that the `Installation Guide` \u003c\u003e_ has fully functional instructions for the deployment of that project.","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"d6121f3b60b07954a3cebd58d9e20cf78f7adb26","unresolved":false,"context_lines":[{"line_number":10,"context_line":"docs:install-guide-verified"},{"line_number":11,"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"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag confirms that the OpenStack manuals team and project confirm this"},{"line_number":14,"context_line":"guide as fully deployable. Specifically, the"},{"line_number":15,"context_line":"`Installation Guide \u003chttps://docs.openstack.org/project-install-guide/draft/\u003e`_"},{"line_number":16,"context_line":"has fully functional and verified instructions for"},{"line_number":17,"context_line":"specific projects. This tag is defined as:"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_e3870ed5","line":14,"range":{"start_line":13,"start_character":62,"end_line":14,"end_character":25},"in_reply_to":"1a1ced50_156f0093","updated":"2017-03-20 16:02:20.000000000","message":"I see your point :) i\u0027ll clarify.","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5f9dc44b09433ff3b37190a4532a6df2475692c6","unresolved":false,"context_lines":[{"line_number":44,"context_line":"ensures that the documentation is verified by the teams each release."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The \"docs:install-guide-verified\" tag is to ensure that, at the very least, a user"},{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"This tag is recommended for the basic projects:"},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_3505dcbb","line":48,"range":{"start_line":47,"start_character":60,"end_line":48,"end_character":62},"updated":"2017-03-20 15:21:10.000000000","message":"This is a fairly large proviso.  I\u0027m not clear on how the timing for this is going to work.  RC-1 isn\u0027t available until R-3, so packages won\u0027t be available prior to that.  I may be misreading what you say later, but it sounds like the deadline for install guide review is the feature freeze, which is usually around R-5.","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"d6121f3b60b07954a3cebd58d9e20cf78f7adb26","unresolved":false,"context_lines":[{"line_number":44,"context_line":"ensures that the documentation is verified by the teams each release."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The \"docs:install-guide-verified\" tag is to ensure that, at the very least, a user"},{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"This tag is recommended for the basic projects:"},{"line_number":51,"context_line":""}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_6374fefc","line":48,"range":{"start_line":47,"start_character":60,"end_line":48,"end_character":62},"in_reply_to":"1a1ced50_3505dcbb","updated":"2017-03-20 16:02:20.000000000","message":"Misread - the deadline to BEGIN the review is to coincide with feature freeze. I\u0027ll also attempt to make this clearer :)","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5f9dc44b09433ff3b37190a4532a6df2475692c6","unresolved":false,"context_lines":[{"line_number":100,"context_line":"     action would also require at least one +1 from a member of the relevant"},{"line_number":101,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":104,"context_line":"  to test installation instructions. It is recommended that the instructions are"},{"line_number":105,"context_line":"  tested for at least one distribution, and the testing level of the other distros"},{"line_number":106,"context_line":"  is documented clearly."}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_b5e8ecb5","line":103,"range":{"start_line":103,"start_character":2,"end_line":103,"end_character":24},"updated":"2017-03-20 15:21:10.000000000","message":"I wonder about the availability of packages at this date, but that\u0027s an empirical question.  Can someone verify that packages are available for testing at R-2?","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"d6121f3b60b07954a3cebd58d9e20cf78f7adb26","unresolved":false,"context_lines":[{"line_number":100,"context_line":"     action would also require at least one +1 from a member of the relevant"},{"line_number":101,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":104,"context_line":"  to test installation instructions. It is recommended that the instructions are"},{"line_number":105,"context_line":"  tested for at least one distribution, and the testing level of the other distros"},{"line_number":106,"context_line":"  is documented clearly."}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_83c81a24","line":103,"range":{"start_line":103,"start_character":2,"end_line":103,"end_character":24},"in_reply_to":"1a1ced50_b5e8ecb5","updated":"2017-03-20 16:02:20.000000000","message":"Packages *usually* are. That\u0027s why I point out that this structure should be \u0027loosely followed\u0027, especially with the assumption that everything is in place.","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5f9dc44b09433ff3b37190a4532a6df2475692c6","unresolved":false,"context_lines":[{"line_number":101,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":104,"context_line":"  to test installation instructions. It is recommended that the instructions are"},{"line_number":105,"context_line":"  tested for at least one distribution, and the testing level of the other distros"},{"line_number":106,"context_line":"  is documented clearly."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"Tag application process"},{"line_number":109,"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"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_95085093","line":106,"range":{"start_line":104,"start_character":37,"end_line":106,"end_character":24},"updated":"2017-03-20 15:21:10.000000000","message":"I can understand not wanting to pick a particular distro from the 3 for all CPLs to use (because that would create a de-facto official distribution), but if people use different distros, we could be in the situation where no single distro has been tested to install correctly for all packages, which would pretty much vitiate this tag.","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"d6121f3b60b07954a3cebd58d9e20cf78f7adb26","unresolved":false,"context_lines":[{"line_number":101,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":102,"context_line":""},{"line_number":103,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":104,"context_line":"  to test installation instructions. It is recommended that the instructions are"},{"line_number":105,"context_line":"  tested for at least one distribution, and the testing level of the other distros"},{"line_number":106,"context_line":"  is documented clearly."},{"line_number":107,"context_line":""},{"line_number":108,"context_line":"Tag application process"},{"line_number":109,"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"}],"source_content_type":"text/x-rst","patch_set":10,"id":"1a1ced50_03042a48","line":106,"range":{"start_line":104,"start_character":37,"end_line":106,"end_character":24},"in_reply_to":"1a1ced50_95085093","updated":"2017-03-20 16:02:20.000000000","message":"Not necessarily, the docs team also test. We are just asking for the CPL in question to test the instructions with at least one distro. Using our matrix, they can tick off those boxes for us and the install-guide team (Lana and her gang) can work on testing the rest :) \nI can clarify this further also","commit_id":"45516c883b849ad04abd688a07adb0eaf25782cd"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"5d49303bcdc6362ee97ce8412c2ab909ad96ed79","unresolved":false,"context_lines":[{"line_number":31,"context_line":""},{"line_number":32,"context_line":"At present, the documentation team is responsible for all documentation in the"},{"line_number":33,"context_line":"openstack/openstack-manuals repo. Maintaining this documentation requires base"},{"line_number":34,"context_line":"knowledge of at least the starter-kit sergices, and occasionally, some of the"},{"line_number":35,"context_line":"optional projects."},{"line_number":36,"context_line":""},{"line_number":37,"context_line":"However, being able to successfully maintain some of the more in-depth"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1a1ced50_54107f01","line":34,"range":{"start_line":34,"start_character":38,"end_line":34,"end_character":46},"updated":"2017-03-21 05:50:15.000000000","message":"services","commit_id":"55d1a809b87283ec6b1a6b2d2c30ed7af542a613"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"c850ff5a7a175904aac4cf4b16e95f4bf6869d08","unresolved":false,"context_lines":[{"line_number":103,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":104,"context_line":"  to test installation instructions. It is recommended that the instructions have been"},{"line_number":105,"context_line":"  tested for at least one distribution by the liaison, and the testing level of the"},{"line_number":106,"context_line":"  other distros is documented clearly. The liaison will work alongside the doc"},{"line_number":107,"context_line":"  team to complete the testing matrix that is available during the release period."},{"line_number":108,"context_line":""},{"line_number":109,"context_line":"Tag application process"},{"line_number":110,"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"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1a1ced50_24512c63","line":107,"range":{"start_line":106,"start_character":39,"end_line":107,"end_character":82},"updated":"2017-03-20 17:00:14.000000000","message":"Brian - I have added this in, but the purpose of this tag is to document what is expected of the project teams, not the docs team. I can add a link to our process if that would help clear this up?","commit_id":"55d1a809b87283ec6b1a6b2d2c30ed7af542a613"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2a24e9da36ede69b32bbbe12f71c2071febbf096","unresolved":false,"context_lines":[{"line_number":11,"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"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag expresses that the OpenStack manuals team and the project"},{"line_number":14,"context_line":"asserting the tag verify that the"},{"line_number":15,"context_line":"`Installation Guide` \u003chttps://docs.openstack.org/project-install-guide/draft/\u003e`_"},{"line_number":16,"context_line":"has fully functional instructions for the deployment of that project."},{"line_number":17,"context_line":"This tag is defined as:"}],"source_content_type":"text/x-rst","patch_set":12,"id":"1a1ced50_12ed2def","line":14,"updated":"2017-03-21 10:56:20.000000000","message":"The team is not asserting the tag (in the way the \"assert\" tags work). I would say:\n\n\"This tag expresses that the OpenStack Documentation team and the project team associated with the tagged deliverable verify that the...\"","commit_id":"84ef471456e9c3b02fa44e5b76706e3e8c806f5b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2a24e9da36ede69b32bbbe12f71c2071febbf096","unresolved":false,"context_lines":[{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"This tag is recommended for the basic projects:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"* Horizon"},{"line_number":53,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":12,"id":"1a1ced50_52a8858d","line":50,"updated":"2017-03-21 10:56:20.000000000","message":"I\u0027m not sure what \"recommended\" means in that context. Could you expand ?","commit_id":"84ef471456e9c3b02fa44e5b76706e3e8c806f5b"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"bfab3b8348551ef73cb183e9ba81f82810320319","unresolved":false,"context_lines":[{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"This tag is recommended for the basic projects:"},{"line_number":51,"context_line":""},{"line_number":52,"context_line":"* Horizon"},{"line_number":53,"context_line":"* Keystone"}],"source_content_type":"text/x-rst","patch_set":12,"id":"1a1ced50_950ca73c","line":50,"in_reply_to":"1a1ced50_52a8858d","updated":"2017-03-21 11:09:20.000000000","message":"Well, I originally went for \u0027required\u0027 but I guess that\u0027s a little vague too. I\u0027ll review again :)","commit_id":"84ef471456e9c3b02fa44e5b76706e3e8c806f5b"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2a24e9da36ede69b32bbbe12f71c2071febbf096","unresolved":false,"context_lines":[{"line_number":113,"context_line":"cycle to coincide with the project team review period."},{"line_number":114,"context_line":""},{"line_number":115,"context_line":"The tag is tentatively added provided the project is on track to release"},{"line_number":116,"context_line":"sufficient documentation, or the tag is removed."},{"line_number":117,"context_line":""},{"line_number":118,"context_line":"Deprecation"},{"line_number":119,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":12,"id":"1a1ced50_320789cb","line":116,"updated":"2017-03-21 10:56:20.000000000","message":"I would make it clearer in this section that the tag is granted by the Docs team.","commit_id":"84ef471456e9c3b02fa44e5b76706e3e8c806f5b"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"52fd45c69b637705c48b457e7d9c3eb717456575","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag expresses that the OpenStack Documentation team and the project team"},{"line_number":14,"context_line":"associated with the tagged deliverable verify that the"},{"line_number":15,"context_line":"`Installation Guide` \u003chttps://docs.openstack.org/project-install-guide/draft/\u003e`_"},{"line_number":16,"context_line":"has fully functional instructions for the deployment of that project."},{"line_number":17,"context_line":"This tag is defined as:"},{"line_number":18,"context_line":""}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_d4d37802","line":15,"range":{"start_line":15,"start_character":19,"end_line":15,"end_character":20},"updated":"2017-03-21 14:52:34.000000000","message":"This backtick is preventing the link from being rendered correctly when the RST is processed.","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a94341c26f0d07a818b0201449b623df26e04c3b","unresolved":false,"context_lines":[{"line_number":12,"context_line":""},{"line_number":13,"context_line":"This tag expresses that the OpenStack Documentation team and the project team"},{"line_number":14,"context_line":"associated with the tagged deliverable verify that the"},{"line_number":15,"context_line":"`Installation Guide` \u003chttps://docs.openstack.org/project-install-guide/draft/\u003e`_"},{"line_number":16,"context_line":"has fully functional instructions for the deployment of that project."},{"line_number":17,"context_line":"This tag is defined as:"},{"line_number":18,"context_line":""}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_9f3919f5","line":15,"range":{"start_line":15,"start_character":19,"end_line":15,"end_character":20},"in_reply_to":"1a1ced50_d4d37802","updated":"2017-03-21 15:38:31.000000000","message":"Good catch!","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"52fd45c69b637705c48b457e7d9c3eb717456575","unresolved":false,"context_lines":[{"line_number":81,"context_line":"  #. The project team is responsible for either:"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":84,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":85,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":86,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_5f4fa16a","line":86,"range":{"start_line":84,"start_character":55,"end_line":86,"end_character":44},"updated":"2017-03-21 14:52:34.000000000","message":"Where are these +1s and +2s being recorded, and how do you envision the sufficient information being conveyed?  It sounds like an email would work -- \"These bugs need to be appropriately documented (bug#, bug#, bug#) and this spec has been implemented (spec url)\".  But in that case, isn\u0027t the fact that the CPL sent it basically a +1?","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a94341c26f0d07a818b0201449b623df26e04c3b","unresolved":false,"context_lines":[{"line_number":81,"context_line":"  #. The project team is responsible for either:"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":84,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":85,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":86,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_71bad10b","line":86,"range":{"start_line":84,"start_character":55,"end_line":86,"end_character":44},"in_reply_to":"1a1ced50_5f4fa16a","updated":"2017-03-21 15:38:31.000000000","message":"As I mentioned when you previously mentioned this, I will document this in our contributor guide and distributed to those that require the knowledge (AKA, all the projects will have a copy etc so we\u0027re all on the same page).\nAlthough I\"m not entirely too sure here by what you\u0027re referring to with \u0027recorded\u0027?","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"34df6413c283a0ac0d6cb16bd430f922ce7d0c0a","unresolved":false,"context_lines":[{"line_number":81,"context_line":"  #. The project team is responsible for either:"},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":84,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":85,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":86,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_47bd1701","line":86,"range":{"start_line":84,"start_character":55,"end_line":86,"end_character":44},"in_reply_to":"1a1ced50_71bad10b","updated":"2017-03-21 16:14:45.000000000","message":"Well, there is some type of artifact where the +1s and +2s show up for public consumption.  What is that artifact?  It\u0027s not a Gerrit review (since that\u0027s dealt with in the next case).  I\u0027m just not clear on where the +1s and +2s you\u0027re talking about in this section and the next are happening.  Gerrit makes it really easy to do the +1 and +2 business, but if this is happening outside of Gerrit, where is it happening?","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"52fd45c69b637705c48b457e7d9c3eb717456575","unresolved":false,"context_lines":[{"line_number":85,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":86,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"},{"line_number":90,"context_line":"       project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"* Project team agrees to ensure that the CPL has reviewed the documentation for"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_df4d513f","line":90,"range":{"start_line":88,"start_character":73,"end_line":90,"end_character":68},"updated":"2017-03-21 14:52:34.000000000","message":"Again, if the CPL puts up a patch, it\u0027s a bit weird to +1 it as well.  But I don\u0027t think you\u0027re talking about the normal patch approvals here, you\u0027re talking more about the CPL and the docs team acknowledging that sufficient info has been provided by the project team.","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"a94341c26f0d07a818b0201449b623df26e04c3b","unresolved":false,"context_lines":[{"line_number":85,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":86,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"},{"line_number":90,"context_line":"       project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"* Project team agrees to ensure that the CPL has reviewed the documentation for"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_5154f5c8","line":90,"range":{"start_line":88,"start_character":73,"end_line":90,"end_character":68},"in_reply_to":"1a1ced50_df4d513f","updated":"2017-03-21 15:38:31.000000000","message":"Yes, I indeed am :)","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"52fd45c69b637705c48b457e7d9c3eb717456575","unresolved":false,"context_lines":[{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  #. Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":102,"context_line":"     action would also require at least one +1 from a member of the relevant"},{"line_number":103,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":106,"context_line":"  to test installation instructions. It is recommended that the instructions have been"}],"source_content_type":"text/x-rst","patch_set":14,"id":"1a1ced50_3fed85ef","line":103,"updated":"2017-03-21 14:52:34.000000000","message":"Same questions as above for both of these.  (I think I\u0027m probably not sufficiently familiar with the docs team processes and there\u0027s a simple answer to this question.)","commit_id":"ae51f009cbe519a91e68ea5bf7141875abde0881"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"4f5ebc29de0efe7878d0d616f2853ef9962a648d","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The \"docs:install-guide-verified\" tag is to ensure that, at the very least, a user"},{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"As the Installation Guide maintained by the documentation team is an"},{"line_number":51,"context_line":"opinionated basic install, we encourage that the following basic projects"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_772d5ca7","line":48,"range":{"start_line":48,"start_character":22,"end_line":48,"end_character":62},"updated":"2017-03-21 18:20:24.000000000","message":"In past discussions, we\u0027ve had the debate about whether this is fair to some of smaller/newer projects that get no attention from distros. It has been voiced in various ops midcycles that packages are not actually the most common way people deploy OpenStack services. I would be hesitant to allow this tag with the current wording.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"4f5ebc29de0efe7878d0d616f2853ef9962a648d","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The \"docs:install-guide-verified\" tag is to ensure that, at the very least, a user"},{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"As the Installation Guide maintained by the documentation team is an"},{"line_number":51,"context_line":"opinionated basic install, we encourage that the following basic projects"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_77fabc44","line":48,"range":{"start_line":48,"start_character":0,"end_line":48,"end_character":8},"updated":"2017-03-21 18:20:24.000000000","message":"provision","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The \"docs:install-guide-verified\" tag is to ensure that, at the very least, a user"},{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"As the Installation Guide maintained by the documentation team is an"},{"line_number":51,"context_line":"opinionated basic install, we encourage that the following basic projects"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_2a228e52","line":48,"range":{"start_line":48,"start_character":0,"end_line":48,"end_character":8},"in_reply_to":"1a1ced50_6625ac07","updated":"2017-03-22 01:55:27.000000000","message":"The packages/source argument will rage on. It will go down in the annals of open source with \"Which *nix to install?\" and \"Which text editor to use?\". We know most people don\u0027t install by hand, and have made changes to the Install Guide to acknowledge that it is to be used for a PoC/training exercise, not a production install. We are also actively seeking deployment projects to document procedures for installing using their tools (since we know this is what most people do). So, this is neither the time nor place to argue about package installs, IMO (by all means, open that can of worms in another forum, though. It\u0027s been a while since I\u0027ve gotten into the middle of a good flamewar). The point of this change is to ensure that the Install Guide is able to be maintained to its current high standards, by formalising a little help from the projects we document. The alternative is that we stop testing the Install Guide altogether, and leave it entirely up to individual projects to respond to RFEs and bug fixes. I\u0027m happy to do that, it would make my job a hell of a lot easier.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":2750,"name":"Sean Dague","email":"sean@dague.net","username":"sdague"},"change_message_id":"c52c2c3ca322c92874b77ed6e3a79b94c39febef","unresolved":false,"context_lines":[{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The \"docs:install-guide-verified\" tag is to ensure that, at the very least, a user"},{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the manuals. This is on the"},{"line_number":48,"context_line":"proviso that there is no issue with the distribution packages."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"As the Installation Guide maintained by the documentation team is an"},{"line_number":51,"context_line":"opinionated basic install, we encourage that the following basic projects"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_6625ac07","line":48,"range":{"start_line":48,"start_character":0,"end_line":48,"end_character":8},"in_reply_to":"1a1ced50_77fabc44","updated":"2017-03-21 20:17:41.000000000","message":"At the ops midcycle, it\u0027s usually kind of 50/50 to my recollection, but we have to admit the ops midcycle is the top 1% of operators in OpenStack. Ones that are committed enough and skilled enough to send someone to this event.\n\nI think that as you get out of that sphere \"just using packages\" dominates.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"4091c70fe7da615df07a2761db170d2c20786dde","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* Cinder"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Any projects that maintain project-specific Installation Guides must have"},{"line_number":62,"context_line":"this tag for their guide to be linked from docs.openstack.org."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Requirements"},{"line_number":65,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_9132e0f0","line":62,"updated":"2017-03-21 20:29:50.000000000","message":"This makes me sad, with the requirement of \"work alongside the docs team to test the\ninstructions\". The reason we have out of tree install guides is because the docs team didn\u0027t have time to do this. I\u0027d be surprised if the docs team suddenly has time to do this, especially in the release rush.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b8e4736b6f3c8dc6dd5e2c9cad802e0151272ae0","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* Cinder"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Any projects that maintain project-specific Installation Guides must have"},{"line_number":62,"context_line":"this tag for their guide to be linked from docs.openstack.org."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Requirements"},{"line_number":65,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_4ae25330","line":62,"in_reply_to":"1a1ced50_4adc2a73","updated":"2017-03-22 13:49:06.000000000","message":"@Tony, right, as Lana says, the docs team does this for the \"basic\" projects. If we make it a requirement for all big tent projects to go through this process to be able to publish their guides, I think it will overwhelm the docs team very quickly.\n\n@Lana thanks, I think that\u0027s the way to go. :)","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"d4fa6231630ac3e1c2e9e5c19f197eb29e610b65","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* Cinder"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Any projects that maintain project-specific Installation Guides must have"},{"line_number":62,"context_line":"this tag for their guide to be linked from docs.openstack.org."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Requirements"},{"line_number":65,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_f4093d85","line":62,"in_reply_to":"1a1ced50_9132e0f0","updated":"2017-03-22 00:39:24.000000000","message":"The docs team *is* doing this ATM for each release on 3 distros.  All this is doing is pulling the project team in to help verify that things are correct.  Say if a project has a version endpoint and the preferred endpoint changes the project team is in the place to catch that.  Likewise if a project adds a new service (*cough* placement) then someone that knows how that works will be on hand to get the instructions right.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":59,"context_line":"* Cinder"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Any projects that maintain project-specific Installation Guides must have"},{"line_number":62,"context_line":"this tag for their guide to be linked from docs.openstack.org."},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"Requirements"},{"line_number":65,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_4adc2a73","line":62,"in_reply_to":"1a1ced50_f4093d85","updated":"2017-03-22 01:55:27.000000000","message":"So, the docs team currently tests the basic projects (as listed) on Ubuntu, RHEL/CentOS, and OpenSUSE/SLES (we\u0027ve dropped Debian from Ocata, as there are no packages). We do not test the guides for optional projects: writing and maintenance of these is up to the project in question. I agree that basic projects should be required to use the tag, this would greatly improve our ability to test (in Ocata, we had to delay testing/branching due to a change in Nova that we had not been made aware of that broke our guide). As for the optional projects, I\u0027m happy for quality control and testing to reside with those projects, as we offer no guarantees.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"4f5ebc29de0efe7878d0d616f2853ef9962a648d","unresolved":false,"context_lines":[{"line_number":64,"context_line":"Requirements"},{"line_number":65,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"To maintain the \"docs:install-guide-verified\" tag, the cross-project liaison (CPL)"},{"line_number":68,"context_line":"must have read the docs and opened appropriate bugs in docs by"},{"line_number":69,"context_line":"the installation guide review deadline, and provided information to the docs team"},{"line_number":70,"context_line":"on how to document these issues."}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_da539515","line":67,"range":{"start_line":67,"start_character":55,"end_line":67,"end_character":77},"updated":"2017-03-21 18:20:24.000000000","message":"might be good to specify which cpl, since there are docs, release, cross-project spec liaisons, etc.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"105753148fcfcb2e84b1b14646b73e13b2da3e40","unresolved":false,"context_lines":[{"line_number":64,"context_line":"Requirements"},{"line_number":65,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"To maintain the \"docs:install-guide-verified\" tag, the cross-project liaison (CPL)"},{"line_number":68,"context_line":"must have read the docs and opened appropriate bugs in docs by"},{"line_number":69,"context_line":"the installation guide review deadline, and provided information to the docs team"},{"line_number":70,"context_line":"on how to document these issues."}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_e6834554","line":67,"range":{"start_line":67,"start_character":55,"end_line":67,"end_character":77},"in_reply_to":"1a1ced50_4ae6ea15","updated":"2017-03-22 10:09:54.000000000","message":"I can adjust to ensure this is clarified. My target here was solely the docs CPL, which, I felt was fairly self explanatory seeing as this is a tag for documentation.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":64,"context_line":"Requirements"},{"line_number":65,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"To maintain the \"docs:install-guide-verified\" tag, the cross-project liaison (CPL)"},{"line_number":68,"context_line":"must have read the docs and opened appropriate bugs in docs by"},{"line_number":69,"context_line":"the installation guide review deadline, and provided information to the docs team"},{"line_number":70,"context_line":"on how to document these issues."}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_4ae6ea15","line":67,"range":{"start_line":67,"start_character":55,"end_line":67,"end_character":77},"in_reply_to":"1a1ced50_da539515","updated":"2017-03-22 01:55:27.000000000","message":"We do currently send the docs CPLs a courtesy ping a few weeks out from release date to check, but most of these go ignored. I\u0027m assuming CPL here is referring to Docs CPL, but if that is the case, it might pay to widen the contact to release CPL and/or PTL, to try and get more feedback.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":83,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":84,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":85,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":86,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_aaa2feab","line":86,"range":{"start_line":86,"start_character":7,"end_line":86,"end_character":44},"updated":"2017-03-22 01:55:27.000000000","message":"Would this information be provided in the form of a patch to the openstack-manuals repo? Wouldn\u0027t a bug report or other form of communication be better? Also, if we\u0027re asking optional projects to use the tag, the content lives in their own repo, where docs cores don\u0027t (necessarily) have +2 rights.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"105753148fcfcb2e84b1b14646b73e13b2da3e40","unresolved":false,"context_lines":[{"line_number":83,"context_line":"     * Providing sufficient information to the documentation team to ensure the"},{"line_number":84,"context_line":"       bug or enhancement is documented appropriately. This action would require"},{"line_number":85,"context_line":"       at least one +1 from a member of the relevant project team (CPL), and"},{"line_number":86,"context_line":"       two +2\u0027s from the documentation team."},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_260d5de8","line":86,"range":{"start_line":86,"start_character":7,"end_line":86,"end_character":44},"in_reply_to":"1a1ced50_aaa2feab","updated":"2017-03-22 10:09:54.000000000","message":"I probably haven\u0027t made this clear enough - so I can rectify that. But I was trying to express that the information could be delivered in a bug, or a patch, and if it came through in a patch, these are the requirements...","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":87,"context_line":""},{"line_number":88,"context_line":"     * Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":89,"context_line":"       action would also require at least one +1 from a member of the relevant"},{"line_number":90,"context_line":"       project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":91,"context_line":""},{"line_number":92,"context_line":""},{"line_number":93,"context_line":"* Project team agrees to ensure that the CPL has reviewed the documentation for"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_0aaeb297","line":90,"range":{"start_line":90,"start_character":31,"end_line":90,"end_character":67},"updated":"2017-03-22 01:55:27.000000000","message":"Again, is this a patch in the openstack-manuals repo? Same concerns as I wrote above.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":96,"context_line":"  #. Provide sufficient information to the documentation team in a bug report to"},{"line_number":97,"context_line":"     ensure the bug or enhancement is documented appropriately. This action"},{"line_number":98,"context_line":"     would require at least one +1 from a member of the relevant project"},{"line_number":99,"context_line":"     team (CPL), and two +2\u0027s from the documentation team."},{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  #. Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":102,"context_line":"     action would also require at least one +1 from a member of the relevant"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_6a9d6665","line":99,"range":{"start_line":99,"start_character":20,"end_line":99,"end_character":57},"updated":"2017-03-22 01:55:27.000000000","message":"And again","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":100,"context_line":""},{"line_number":101,"context_line":"  #. Or, the project team patches up a fix for the bug or enhancement. This"},{"line_number":102,"context_line":"     action would also require at least one +1 from a member of the relevant"},{"line_number":103,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":106,"context_line":"  to test installation instructions. It is recommended that the instructions have been"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_8a9aa26c","line":103,"range":{"start_line":103,"start_character":28,"end_line":103,"end_character":65},"updated":"2017-03-22 01:55:27.000000000","message":"And again","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":102,"context_line":"     action would also require at least one +1 from a member of the relevant"},{"line_number":103,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":106,"context_line":"  to test installation instructions. It is recommended that the instructions have been"},{"line_number":107,"context_line":"  tested for at least one distribution by the liaison, and the testing level of the"},{"line_number":108,"context_line":"  other distros is documented clearly. The liaison will work alongside the doc"},{"line_number":109,"context_line":"  team to complete the testing matrix that is available during the release period."}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_8a71c246","line":106,"range":{"start_line":105,"start_character":26,"end_line":106,"end_character":36},"updated":"2017-03-22 01:55:27.000000000","message":"Oh, how I would love for this to be true!","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"105753148fcfcb2e84b1b14646b73e13b2da3e40","unresolved":false,"context_lines":[{"line_number":102,"context_line":"     action would also require at least one +1 from a member of the relevant"},{"line_number":103,"context_line":"     project team (CPL), and two +2\u0027s from the documentation team."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":106,"context_line":"  to test installation instructions. It is recommended that the instructions have been"},{"line_number":107,"context_line":"  tested for at least one distribution by the liaison, and the testing level of the"},{"line_number":108,"context_line":"  other distros is documented clearly. The liaison will work alongside the doc"},{"line_number":109,"context_line":"  team to complete the testing matrix that is available during the release period."}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_86f8d1c4","line":106,"range":{"start_line":105,"start_character":26,"end_line":106,"end_character":36},"in_reply_to":"1a1ced50_8a71c246","updated":"2017-03-22 10:09:54.000000000","message":"Well, that\u0027s what we\u0027re trying to achieve ;)","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"2616363e38a84274d80617bb9937605f54a7adc0","unresolved":false,"context_lines":[{"line_number":106,"context_line":"  to test installation instructions. It is recommended that the instructions have been"},{"line_number":107,"context_line":"  tested for at least one distribution by the liaison, and the testing level of the"},{"line_number":108,"context_line":"  other distros is documented clearly. The liaison will work alongside the doc"},{"line_number":109,"context_line":"  team to complete the testing matrix that is available during the release period."},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"Tag application process"},{"line_number":112,"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"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_f1bcf4bc","line":109,"updated":"2017-03-21 20:47:37.000000000","message":"This seems like it could become a major bottleneck, once more projects begin to get on board.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"b8e4736b6f3c8dc6dd5e2c9cad802e0151272ae0","unresolved":false,"context_lines":[{"line_number":106,"context_line":"  to test installation instructions. It is recommended that the instructions have been"},{"line_number":107,"context_line":"  tested for at least one distribution by the liaison, and the testing level of the"},{"line_number":108,"context_line":"  other distros is documented clearly. The liaison will work alongside the doc"},{"line_number":109,"context_line":"  team to complete the testing matrix that is available during the release period."},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"Tag application process"},{"line_number":112,"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"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_2a6c379b","line":109,"in_reply_to":"1a1ced50_26db9d50","updated":"2017-03-22 13:49:06.000000000","message":"The bottleneck I see is bringing in the docs team to help with testing each guide, along with the requirement above for project-specific guides to earn this tag to be able to publish.\n\nThere\u0027s over 50 big tent projects - is it realistic for the docs team to help test all of them?\n\n(It looks like this is somewhat addressed in the next patch set - I\u0027ll comment further there)","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"105753148fcfcb2e84b1b14646b73e13b2da3e40","unresolved":false,"context_lines":[{"line_number":106,"context_line":"  to test installation instructions. It is recommended that the instructions have been"},{"line_number":107,"context_line":"  tested for at least one distribution by the liaison, and the testing level of the"},{"line_number":108,"context_line":"  other distros is documented clearly. The liaison will work alongside the doc"},{"line_number":109,"context_line":"  team to complete the testing matrix that is available during the release period."},{"line_number":110,"context_line":""},{"line_number":111,"context_line":"Tag application process"},{"line_number":112,"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"}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_26db9d50","line":109,"in_reply_to":"1a1ced50_f1bcf4bc","updated":"2017-03-22 10:09:54.000000000","message":"Explain how you feel this is so? Currently, the biggest bottleneck is that the guide is unworkable, and unable to branch over a month after release because we have guides that do not install. That\u0027s a bigger bottleneck than each project testing their instructions and assisting us fill in our matrix.\nHere\u0027s the Ocata matrix so you can see what we\u0027re referring to: https://wiki.openstack.org/wiki/Documentation/NewtonDocTesting","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":9162,"name":"Lana Brindley","email":"openstack@lanabrindley.com","username":"loquacity"},"change_message_id":"1cecc1ded9b867a02193fe0f3ace64776add6e23","unresolved":false,"context_lines":[{"line_number":120,"context_line":"Deprecation"},{"line_number":121,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":122,"context_line":""},{"line_number":123,"context_line":"Documentation for each team will be reviewed by the docs team after each cycle."},{"line_number":124,"context_line":"If there are issues, there would be a discussion and if the issues are not"},{"line_number":125,"context_line":"resolved the tag will be removed."},{"line_number":126,"context_line":""}],"source_content_type":"text/x-rst","patch_set":15,"id":"1a1ced50_cabc9abd","line":123,"range":{"start_line":123,"start_character":62,"end_line":123,"end_character":78},"updated":"2017-03-22 01:55:27.000000000","message":"Docs test the Install Guide in the four-or-so weeks leading up to release, and continue until we branch three-or-so weeks after release.","commit_id":"305a4ff9de5eb8c7b880d2d2a6d74487d1a80678"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"2074645d98d96bba8310f357f02709b69f060885","unresolved":false,"context_lines":[{"line_number":58,"context_line":"* Neutron"},{"line_number":59,"context_line":"* Cinder"},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"The aim of this tag is to pull the above project teams in to help verify that the"},{"line_number":62,"context_line":"instructions are correct. For example, if a project has a version endpoint and"},{"line_number":63,"context_line":"the preferred endpoint changes, the project team is in the place to catch that"},{"line_number":64,"context_line":"and ensure the instructions are correct. This is designed to benefit the user"},{"line_number":65,"context_line":"and operating referencing the guides."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"The install guides written by the optional projects are not currently tested by"},{"line_number":68,"context_line":"the documentation team; the writing and maintenance is left up to the project"},{"line_number":69,"context_line":"in question. However, we do encourage any projects that maintain project-specific"},{"line_number":70,"context_line":"Installation Guides use this tag."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"The tag would be applied, for the first time (and subsequent releases"},{"line_number":73,"context_line":"afterwards), at the Pike release: R+0"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1a1ced50_4afed3ae","line":70,"range":{"start_line":61,"start_character":0,"end_line":70,"end_character":33},"updated":"2017-03-22 13:48:48.000000000","message":"I like this addition, should we require testing sign-off from them as well? You might need to expand your section below for these as well.\n\nAnd instead of optional projects, call them somethign like install guides living in project repos but following the overall installation guides architecture (links to spec or contributor guide?).","commit_id":"1ddee06411d3b043209e69607e13d6371fe4c665"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"2074645d98d96bba8310f357f02709b69f060885","unresolved":false,"context_lines":[{"line_number":74,"context_line":"For any projects that are following the trailing release schedule, it would"},{"line_number":75,"context_line":"be applied at R+2."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"When the new branch is cut for openstack-manuals, (approx. 3 weeks after release)"},{"line_number":78,"context_line":"the tag would be removed for the /draft/ (master) branch"},{"line_number":79,"context_line":"(https://docs.openstack.org/draft/draft-index.html), but would be applicable for"},{"line_number":80,"context_line":"\"Ocata\" until \"Pike\" is published."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Requirements"},{"line_number":83,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1a1ced50_caf563ed","line":80,"range":{"start_line":77,"start_character":0,"end_line":80,"end_character":34},"updated":"2017-03-22 13:48:48.000000000","message":"Better give docs.openstack.org/project-install-guide/... as link. We would remove content from those documents based on the tags used.","commit_id":"1ddee06411d3b043209e69607e13d6371fe4c665"},{"author":{"_account_id":6547,"name":"Andreas Jaeger","email":"jaegerandi@gmail.com","username":"jaegerandi"},"change_message_id":"2074645d98d96bba8310f357f02709b69f060885","unresolved":false,"context_lines":[{"line_number":103,"context_line":"       in Launchpad to ensure the bug/enhancement is documented appropriately."},{"line_number":104,"context_line":""},{"line_number":105,"context_line":"     * Or, the project team patches up a fix to the openstack-manuals repo for the"},{"line_number":106,"context_line":"       bug/enhancement. If this is fixed in a patch, this action would require"},{"line_number":107,"context_line":"       at least one +1 from a member of the relevant project team (CPL or PTL),"},{"line_number":108,"context_line":"       and two +2\u0027s from the documentation team (as per the norm)."},{"line_number":109,"context_line":""},{"line_number":110,"context_line":"* Project team agrees to ensure that the liaison has reviewed the documentation for"},{"line_number":111,"context_line":"  the team project 4 weeks before the release, and either:"}],"source_content_type":"text/x-rst","patch_set":16,"id":"1a1ced50_2abef7fe","line":108,"range":{"start_line":106,"start_character":24,"end_line":108,"end_character":66},"updated":"2017-03-22 13:48:48.000000000","message":"Why not just say: The documentation team might will require an additional +1 by the relevant project team for such issues before approval.","commit_id":"1ddee06411d3b043209e69607e13d6371fe4c665"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"26ccb8da374fd7e6704a9578313b59c5c137f707","unresolved":false,"context_lines":[{"line_number":67,"context_line":"The other installation guides that are living in project repos are not"},{"line_number":68,"context_line":"currently tested by the documentation team; the writing and maintenance is left"},{"line_number":69,"context_line":"up to the (optional) project in question. However, we do encourage any projects"},{"line_number":70,"context_line":"that maintain project-specific Installation Guides use this tag."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"The tag would be applied, for the first time (and subsequent releases"},{"line_number":73,"context_line":"afterwards), at the Pike release: R+0"}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a1ced50_7566102b","line":70,"updated":"2017-03-22 14:13:45.000000000","message":"For the \"other\" projects, do we follow the same requirements below to apply for the tag? The reason we have install guides in the project repos is because the docs team doesn\u0027t have time to review and test the guides. I assume the docs team also won\u0027t have time to help \"other\" projects with the below requirements.\n\nSo it seems some teams will be at a disadvantage here. On the other hand, I don\u0027t want to have a different bar for different projects. So I\u0027m kind of stuck on what to do here. :(","commit_id":"3fab154364d7bc6e92917b241a179f29bdfde2c8"},{"author":{"_account_id":10343,"name":"Jim Rollenhagen","email":"jim@jimrollenhagen.com","username":"jimrollenhagen"},"change_message_id":"215767e1ce277cc0d50fd35f17c48880869e36a8","unresolved":false,"context_lines":[{"line_number":67,"context_line":"The other installation guides that are living in project repos are not"},{"line_number":68,"context_line":"currently tested by the documentation team; the writing and maintenance is left"},{"line_number":69,"context_line":"up to the (optional) project in question. However, we do encourage any projects"},{"line_number":70,"context_line":"that maintain project-specific Installation Guides use this tag."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"The tag would be applied, for the first time (and subsequent releases"},{"line_number":73,"context_line":"afterwards), at the Pike release: R+0"}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a1ced50_ec291f39","line":70,"in_reply_to":"1a1ced50_2d1fc85b","updated":"2017-03-23 16:12:27.000000000","message":"+1 for being explicit. Alex, thanks for posting the result of our conversation here. Thierry, great suggestion. :)","commit_id":"3fab154364d7bc6e92917b241a179f29bdfde2c8"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"d20ff2eca95d9a7f326237d0a5b88390e658efef","unresolved":false,"context_lines":[{"line_number":67,"context_line":"The other installation guides that are living in project repos are not"},{"line_number":68,"context_line":"currently tested by the documentation team; the writing and maintenance is left"},{"line_number":69,"context_line":"up to the (optional) project in question. However, we do encourage any projects"},{"line_number":70,"context_line":"that maintain project-specific Installation Guides use this tag."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"The tag would be applied, for the first time (and subsequent releases"},{"line_number":73,"context_line":"afterwards), at the Pike release: R+0"}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a1ced50_2d1fc85b","line":70,"in_reply_to":"1a1ced50_30dbc61c","updated":"2017-03-23 09:20:57.000000000","message":"I see what you\u0027re saying, but I also think the current wording doesn\u0027t explain the situation for those projects enough (hence Jim\u0027s question).\n\nSo I\u0027d say something like \"we do encourage projects that maintain project-specific Installation Guides to apply for this tag as well. It would signal that they commit to provide functioning installation guides every release. In that case, the docs team would only do cursory checks to check that the tag wasn\u0027t misplaced.\"","commit_id":"3fab154364d7bc6e92917b241a179f29bdfde2c8"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"10db11746a481dc7007ae2ac49c648e0b7b347b4","unresolved":false,"context_lines":[{"line_number":67,"context_line":"The other installation guides that are living in project repos are not"},{"line_number":68,"context_line":"currently tested by the documentation team; the writing and maintenance is left"},{"line_number":69,"context_line":"up to the (optional) project in question. However, we do encourage any projects"},{"line_number":70,"context_line":"that maintain project-specific Installation Guides use this tag."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"The tag would be applied, for the first time (and subsequent releases"},{"line_number":73,"context_line":"afterwards), at the Pike release: R+0"}],"source_content_type":"text/x-rst","patch_set":17,"id":"1a1ced50_30dbc61c","line":70,"in_reply_to":"1a1ced50_7566102b","updated":"2017-03-22 14:26:19.000000000","message":"Repeating what we just discussed on IRC for everyone else:\n\nThe reason we\u0027re needing the large review process for the 6 projects specifically is because we need their changes to go through our repo. However, the optional projects do not. Provided that before the release that the CPL for $PROJECT with a guide linked to the project-install-guide page can verify it is in working order, we give them the tag. If they are unable to establish a deploy, then the guide is taken away.\n\nThe biggest concern at the moment is that we\u0027re not receiving reviews from the projects and that\u0027s leaving us with outdated and incorrect content. If the optional project team\u0027s CPL verifies a working guide, I see no reason why we cannot provide the tag.\n\nIt offers a simple, fair, solution.\n\nAlthough I am very open to hearing more :)","commit_id":"3fab154364d7bc6e92917b241a179f29bdfde2c8"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"cbf6629cf052af9b722dd2f8ff29535613d7b29c","unresolved":false,"context_lines":[{"line_number":4,"context_line":"  Unported License."},{"line_number":5,"context_line":"  http://creativecommons.org/licenses/by/3.0/legalcode"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":".. _`tag-docs:install-guide-verified`"},{"line_number":8,"context_line":""},{"line_number":9,"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"},{"line_number":10,"context_line":"docs:install-guide-verified"}],"source_content_type":"text/x-rst","patch_set":19,"id":"ffe62b97_71c17b2e","line":7,"range":{"start_line":7,"start_character":0,"end_line":7,"end_character":37},"updated":"2017-03-27 13:30:29.000000000","message":"docs_install-guide-verified.rst:7: WARNING: malformed hyperlink target.\n\n\nThis is new?","commit_id":"29f0827830957d94e5cb5e131bec3fb5c9a65633"},{"author":{"_account_id":170,"name":"Mike Perez","email":"thingee@gmail.com","username":"thingee"},"change_message_id":"c813522ee6373e977ffe9764a0d9b156e78b599f","unresolved":false,"context_lines":[{"line_number":43,"context_line":"all necessary major bug fixes and enhancements. However, this method no longer"},{"line_number":44,"context_line":"ensures that the documentation is verified by the teams each release."},{"line_number":45,"context_line":""},{"line_number":46,"context_line":"The \"docs:install-guide-verified\" tag is to ensure that, at the very least, a user"},{"line_number":47,"context_line":"is able to successfully deploy OpenStack using the OpenStack manuals"},{"line_number":48,"context_line":"installation guides published at docs.openstack.org."},{"line_number":49,"context_line":""},{"line_number":50,"context_line":"As the Installation Guide maintained by the documentation team is an"},{"line_number":51,"context_line":"opinionated basic install, we encourage that the following projects"}],"source_content_type":"text/x-rst","patch_set":21,"id":"ffe62b97_f54c459f","line":48,"range":{"start_line":46,"start_character":0,"end_line":48,"end_character":52},"updated":"2017-03-27 19:26:45.000000000","message":"What about the deployment guides?","commit_id":"3778a23aa16ca3d17a014860fa61ac1df0a2f51e"},{"author":{"_account_id":6873,"name":"Matt Riedemann","email":"mriedem.os@gmail.com","username":"mriedem"},"change_message_id":"b3049f00fd3426a6f521c0e2164ce1a992168fd5","unresolved":false,"context_lines":[{"line_number":62,"context_line":"instructions are correct. For example, if a project has a version endpoint and"},{"line_number":63,"context_line":"the preferred endpoint changes, the project team is in the place to catch that"},{"line_number":64,"context_line":"and ensure the instructions are correct. This is designed to benefit the user"},{"line_number":65,"context_line":"and operating referencing the guides."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"We encourage projects that maintain project-specific Installation Guides to"},{"line_number":68,"context_line":"apply for this tag as well. It would signal that they commit to provide"}],"source_content_type":"text/x-rst","patch_set":21,"id":"ffe62b97_95ea99a9","line":65,"range":{"start_line":65,"start_character":4,"end_line":65,"end_character":13},"updated":"2017-03-27 18:56:29.000000000","message":"operator","commit_id":"3778a23aa16ca3d17a014860fa61ac1df0a2f51e"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"028e614578b26accc969ed9954fe61c0261c6d2e","unresolved":false,"context_lines":[{"line_number":74,"context_line":"For any projects that are following the trailing release schedule, it would"},{"line_number":75,"context_line":"be applied at R+2."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"When the new branch is cut for openstack-manuals, (approx. 3 weeks after release)"},{"line_number":78,"context_line":"the tag would be removed for the /draft/ (master) branch"},{"line_number":79,"context_line":"(https://docs.openstack.org/draft/draft-index.html), but would be applicable for"},{"line_number":80,"context_line":"\"Ocata\" until \"Pike\" is published."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Requirements"},{"line_number":83,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":21,"id":"ffe62b97_47f9124b","line":80,"range":{"start_line":77,"start_character":0,"end_line":80,"end_character":34},"updated":"2017-03-27 15:17:42.000000000","message":"I\u0027m confused by this.  The tags for each project \"live\" in the projects.yaml in the governance repo.  So for Pike, assuming Glance complies, glance will have the \u0027docs:install-guide-verified\u0027 added to its list of tags in projects.yaml at R+0.  Then this will be removed from projects.yaml 3 weeks later.  Are you talking about a list somewhere on the install docs themselves indicating that the docs for Pike have been verified by top professionals?","commit_id":"3778a23aa16ca3d17a014860fa61ac1df0a2f51e"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"16eb0708668a0b5fb8ddd54eefa35a6c6bd70d48","unresolved":false,"context_lines":[{"line_number":74,"context_line":"For any projects that are following the trailing release schedule, it would"},{"line_number":75,"context_line":"be applied at R+2."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"When the new branch is cut for openstack-manuals, (approx. 3 weeks after release)"},{"line_number":78,"context_line":"the tag would be removed for the /draft/ (master) branch"},{"line_number":79,"context_line":"(https://docs.openstack.org/draft/draft-index.html), but would be applicable for"},{"line_number":80,"context_line":"\"Ocata\" until \"Pike\" is published."},{"line_number":81,"context_line":""},{"line_number":82,"context_line":"Requirements"},{"line_number":83,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":21,"id":"ffe62b97_73cbb871","line":80,"range":{"start_line":77,"start_character":0,"end_line":80,"end_character":34},"in_reply_to":"ffe62b97_47f9124b","updated":"2017-03-27 16:15:22.000000000","message":"That\u0027s more or less what I\u0027m insinuating, yes. So, once the $NEXT_RELEASE branch is cut, we remove from the projects.yaml, and then we addd a notation to the guide that all content within is verified or something similar.\nWe should probably hash that out.\n\nGood question, Brian :)","commit_id":"3778a23aa16ca3d17a014860fa61ac1df0a2f51e"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"7384d9a429157527803dee4d2ab32c667cb21411","unresolved":false,"context_lines":[{"line_number":62,"context_line":"instructions are correct. For example, if a project has a version endpoint and"},{"line_number":63,"context_line":"the preferred endpoint changes, the project team is in the place to catch that"},{"line_number":64,"context_line":"and ensure the instructions are correct. This is designed to benefit the user"},{"line_number":65,"context_line":"and operating referencing the guides."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"We encourage projects that maintain project-specific Installation Guides to"},{"line_number":68,"context_line":"apply for this tag as well. It would signal that they commit to provide"}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_dbe32ba4","line":65,"updated":"2017-03-30 20:36:24.000000000","message":"This used to be the section that talked about the tag being \"required\" for these projects. I like the change in tone that this version represents, but now I wonder what happens if the teams don\u0027t follow through? Would it be better to not list specific projects here and just say that both types of projects (those included in the guide managed by the docs team and those with standalone guides) are encouraged to apply for the tag?","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"cbe22a384bb4e096b0773b971f0e1674e7cbc4f8","unresolved":false,"context_lines":[{"line_number":62,"context_line":"instructions are correct. For example, if a project has a version endpoint and"},{"line_number":63,"context_line":"the preferred endpoint changes, the project team is in the place to catch that"},{"line_number":64,"context_line":"and ensure the instructions are correct. This is designed to benefit the user"},{"line_number":65,"context_line":"and operating referencing the guides."},{"line_number":66,"context_line":""},{"line_number":67,"context_line":"We encourage projects that maintain project-specific Installation Guides to"},{"line_number":68,"context_line":"apply for this tag as well. It would signal that they commit to provide"}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_17544c20","line":65,"in_reply_to":"dfeb2761_dbe32ba4","updated":"2017-04-04 13:33:07.000000000","message":"Hmmm, I would like to encourage it for others, and ensure it\u0027s required for the above as that reflects our current model.\nThe reason I *need* the tag to be applicable for the above projects is because they don\u0027t maintain it themselves. SO we\u0027d be going backwards if we just encouraged it for all projects - IMHO, anyway.","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"21f7eb3449f8bb76775d86103d4b079fcdcc7445","unresolved":false,"context_lines":[{"line_number":69,"context_line":"functioning installation guides every release. In that case, the docs team"},{"line_number":70,"context_line":"would only do cursory checks to check that the tag wasn\u0027t misplaced."},{"line_number":71,"context_line":""},{"line_number":72,"context_line":"We also encourage deployment projects that maintain project-specific Deployment"},{"line_number":73,"context_line":"Guides to apply for this tag as well. It would signal that they commit to provide"},{"line_number":74,"context_line":"functioning deployment guides every release. In that case, the docs team"},{"line_number":75,"context_line":"would only do cursory checks to check that the tag wasn\u0027t misplaced."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"The tag would be applied, for the first time (and subsequent releases"},{"line_number":78,"context_line":"afterwards), at the Pike release: R+0"}],"source_content_type":"text/x-rst","patch_set":22,"id":"ffe62b97_1681d3c3","line":75,"range":{"start_line":72,"start_character":0,"end_line":75,"end_character":68},"updated":"2017-03-28 10:56:51.000000000","message":"For deployment projects. I don\u0027t see how we can further include them anymore than this :) this keeps the same barrier to entry as the other projects that are using the project-specific install process.\n\nIt is only the projects above that are required to work with the docs team in the docs repo.","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"7384d9a429157527803dee4d2ab32c667cb21411","unresolved":false,"context_lines":[{"line_number":82,"context_line":"When the new branch is cut for openstack-manuals, (approx. 3 weeks after release)"},{"line_number":83,"context_line":"the tag would be removed for the /draft/ (master) branch"},{"line_number":84,"context_line":"(https://docs.openstack.org/draft/draft-index.html), but would be applicable for"},{"line_number":85,"context_line":"\"Ocata\" until \"Pike\" is published."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Requirements"},{"line_number":88,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_9b4b6386","line":85,"updated":"2017-03-30 20:36:24.000000000","message":"I think this emphasis on adding and removing the tag every cycle is going to result in a lot of useless churn here in the governance repository, and starts off with a negative assumption that project teams will fail to follow through and have to be monitored in order to do this work. We have plenty of other tags in which teams assert that they follow a policy we have decided is something to encourage within the community (stable:follows-policy, and all of the assert:* tags) and for which we review compliance regularly but do not automatically remove and re-add the tag each cycle. I would prefer if we could follow that pattern with this tag as well. Add the tag when a team earns it, and remove the tag when they stop following the policies that allow them to keep it.\n\nIf we want to track on a per-series basis whether a specific guide was verified, why not do that in the place the user is most naturally going to find the information: the guide they are reading.","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"cbe22a384bb4e096b0773b971f0e1674e7cbc4f8","unresolved":false,"context_lines":[{"line_number":82,"context_line":"When the new branch is cut for openstack-manuals, (approx. 3 weeks after release)"},{"line_number":83,"context_line":"the tag would be removed for the /draft/ (master) branch"},{"line_number":84,"context_line":"(https://docs.openstack.org/draft/draft-index.html), but would be applicable for"},{"line_number":85,"context_line":"\"Ocata\" until \"Pike\" is published."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Requirements"},{"line_number":88,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_9a59a136","line":85,"in_reply_to":"dfeb2761_5dab771c","updated":"2017-04-04 13:33:07.000000000","message":"I will remove this bit :)","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"bc5a791aa9d889aa136d304eb3d8c919121ea73c","unresolved":false,"context_lines":[{"line_number":82,"context_line":"When the new branch is cut for openstack-manuals, (approx. 3 weeks after release)"},{"line_number":83,"context_line":"the tag would be removed for the /draft/ (master) branch"},{"line_number":84,"context_line":"(https://docs.openstack.org/draft/draft-index.html), but would be applicable for"},{"line_number":85,"context_line":"\"Ocata\" until \"Pike\" is published."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Requirements"},{"line_number":88,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_5dab771c","line":85,"in_reply_to":"dfeb2761_6fe690eb","updated":"2017-03-31 12:48:42.000000000","message":"Right. That split also lets us focus on documenting the expectations for the relationships between the teams here, which is what the governance repository is supposed to be for.","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"86e05b00c4b743c42a82307135e160dc0bb1b715","unresolved":false,"context_lines":[{"line_number":82,"context_line":"When the new branch is cut for openstack-manuals, (approx. 3 weeks after release)"},{"line_number":83,"context_line":"the tag would be removed for the /draft/ (master) branch"},{"line_number":84,"context_line":"(https://docs.openstack.org/draft/draft-index.html), but would be applicable for"},{"line_number":85,"context_line":"\"Ocata\" until \"Pike\" is published."},{"line_number":86,"context_line":""},{"line_number":87,"context_line":"Requirements"},{"line_number":88,"context_line":"\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_6fe690eb","line":85,"in_reply_to":"dfeb2761_9b4b6386","updated":"2017-03-31 02:12:06.000000000","message":"This is a great idea, and solves the problem of how a consumer would know that a guide had been verified.  On the original proposal, once the tag is removed 3 weeks out, there\u0027s no way for a reader to know whether the current manual is verified or not.  And when the tag is applied for Pike, say, a consumer of the Newton install guide may be under the impression that it\u0027s been verified since the projects have the tags.\n\nI think it makes sense to sort out two things:\n\n(1) each participating project having a nice shiny docs:install-guide-verified tag to display in their repo, which would be release-independent (but subject to removal if participation stops)\n\n(2) a list somewhere in the preface to the install docs saying which teams have participated in the verification of the installation instructions for that particular release","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":2472,"name":"Doug Hellmann","email":"dhellmann@redhat.com","username":"doug-hellmann"},"change_message_id":"bc5a791aa9d889aa136d304eb3d8c919121ea73c","unresolved":false,"context_lines":[{"line_number":98,"context_line":""},{"line_number":99,"context_line":"The installation guide review deadline will coincide with feature freeze,"},{"line_number":100,"context_line":"which will be viewable in the official schedule."},{"line_number":101,"context_line":""},{"line_number":102,"context_line":"* 6 weeks before release: The liaison has made the docs team"},{"line_number":103,"context_line":"  aware of all major new features and bug fixes up till this point."},{"line_number":104,"context_line":""}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_002d8494","line":101,"updated":"2017-03-31 12:48:42.000000000","message":"I would prefer if the rest of this section talked about the actions that need to be taken, but not describe the details of the schedule or timeline, even as an example. We want to ensure we have covered the expectations, and I think we\u0027re going to get bogged down here in discussions of whether timelines are realistic or not instead of the details of what folks are being asked to do.\n\nInstead of dates or numbers of weeks, say something like \"following the schedule posted by the documentation team\" and then put the deadlines on releases.o.o along with all of the other deadlines. Here, focus on things like \"The project team will provide detailed bug reports or corrections for issues in the documentation.\" and \"The project team will provide summaries of new features that need to be reflected in the documentation.\" (or however you want to say those things).","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"},{"author":{"_account_id":10607,"name":"Alexandra Settle","email":"a.settle@outlook.com","username":"asettle"},"change_message_id":"8a5df62b5b19336324994865f3e8ecbb622a5df0","unresolved":false,"context_lines":[{"line_number":123,"context_line":""},{"line_number":124,"context_line":""},{"line_number":125,"context_line":"* 2 weeks before release: The CPL has worked alongside the documentation release team"},{"line_number":126,"context_line":"  to test installation instructions. It is recommended that the instructions have been"},{"line_number":127,"context_line":"  tested for at least one distribution by the liaison. The liaison will work alongside"},{"line_number":128,"context_line":"  the doc team to complete the testing matrix that is available during the release period."},{"line_number":129,"context_line":"  For example, the Ocata release schedule:"},{"line_number":130,"context_line":"  https://wiki.openstack.org/wiki/Documentation/OcataDocTesting"}],"source_content_type":"text/x-rst","patch_set":22,"id":"dfeb2761_20d3e83a","line":127,"range":{"start_line":126,"start_character":37,"end_line":127,"end_character":53},"updated":"2017-03-31 12:58:49.000000000","message":"\"the liaison assists with testing\"","commit_id":"ffeb49e6803a1f2b525aa27b34e9dffdbd24bb28"}],"reference/tags/index.rst":[{"author":{"_account_id":12898,"name":"Tony Breeds","email":"tony@bakeyournoodle.com","username":"tonyb"},"change_message_id":"5d49303bcdc6362ee97ce8412c2ab909ad96ed79","unresolved":false,"context_lines":[{"line_number":85,"context_line":".. toctree::"},{"line_number":86,"context_line":"   :maxdepth: 1"},{"line_number":87,"context_line":""},{"line_number":88,"context_line":"   doc-approved-tag.rst"}],"source_content_type":"text/x-rst","patch_set":11,"id":"1a1ced50_54595ffd","line":88,"range":{"start_line":88,"start_character":3,"end_line":88,"end_character":23},"updated":"2017-03-21 05:50:15.000000000","message":"docs_install-guide-verified  As the file with the tag description has changed this needs to be updated to match:\n\n docs_install-guide-verified","commit_id":"55d1a809b87283ec6b1a6b2d2c30ed7af542a613"}]}
