)]}'
{"reference/comparison-of-official-group-structures.rst":[{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"cbf13c4c1da05c479e38e36515766fb8524c6b72","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"SIGs can own git repositories and produce software, but that software will be"},{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs are not part of the coordinated release, and will not leverage the release"},{"line_number":71,"context_line":"tooling. Each SIG is responsible for its release management/tagging."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f560f44_044bdb5e","line":70,"range":{"start_line":70,"start_character":0,"end_line":70,"end_character":4},"updated":"2020-09-18 16:44:56.000000000","message":"I would say \"SIGs deliverables are not part of the coordinated release\" -- SIGs are groups of people :)","commit_id":"03e08352337eb23c718e29ce2e91ff4d7177ce41"},{"author":{"_account_id":16708,"name":"Kendall Nelson","display_name":"Kendall (diablo_rojo)","email":"kennelson11@gmail.com","username":"kjnelson"},"change_message_id":"454015e26562fadb40e0b298a7e12bde386d2739","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"SIGs can own git repositories and produce software, but that software will be"},{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs are not part of the coordinated release, and will not leverage the release"},{"line_number":71,"context_line":"tooling. Each SIG is responsible for its release management/tagging."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."}],"source_content_type":"text/x-rst","patch_set":1,"id":"fffc6b78_a99de35a","line":70,"range":{"start_line":70,"start_character":0,"end_line":70,"end_character":4},"in_reply_to":"9f560f44_044bdb5e","updated":"2020-11-19 21:33:43.000000000","message":"Done","commit_id":"03e08352337eb23c718e29ce2e91ff4d7177ce41"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"cbf13c4c1da05c479e38e36515766fb8524c6b72","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"SIGs can own git repositories and produce software, but that software will be"},{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs are not part of the coordinated release, and will not leverage the release"},{"line_number":71,"context_line":"tooling. Each SIG is responsible for its release management/tagging."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f560f44_a4430f3f","line":71,"range":{"start_line":70,"start_character":72,"end_line":71,"end_character":7},"updated":"2020-09-18 16:44:56.000000000","message":"I would say \"not leverage the openstack/releases repository\" since they are using other parts of release tooling, like the release Zuul jobs.","commit_id":"03e08352337eb23c718e29ce2e91ff4d7177ce41"},{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"001fb2eb20df023048eb6abab7ff720ff98c78bf","unresolved":false,"context_lines":[{"line_number":66,"context_line":"liaisons."},{"line_number":67,"context_line":""},{"line_number":68,"context_line":"SIGs can own git repositories and produce software, but that software will be"},{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs are not part of the coordinated release, and will not leverage the release"},{"line_number":71,"context_line":"tooling. Each SIG is responsible for its release management/tagging."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"9f560f44_4f3cd1e0","line":71,"range":{"start_line":69,"start_character":70,"end_line":71,"end_character":68},"updated":"2020-09-18 14:01:47.000000000","message":"What\u0027s about if they decide to pass by the release management? I mean do you think this kind of scenario is possible and do we need to clarify this point too?","commit_id":"03e08352337eb23c718e29ce2e91ff4d7177ce41"},{"author":{"_account_id":16708,"name":"Kendall Nelson","display_name":"Kendall (diablo_rojo)","email":"kennelson11@gmail.com","username":"kjnelson"},"change_message_id":"454015e26562fadb40e0b298a7e12bde386d2739","unresolved":false,"context_lines":[{"line_number":67,"context_line":""},{"line_number":68,"context_line":"SIGs can own git repositories and produce software, but that software will be"},{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs are not part of the coordinated release, and will not leverage the release"},{"line_number":71,"context_line":"tooling. Each SIG is responsible for its release management/tagging."},{"line_number":72,"context_line":""},{"line_number":73,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."},{"line_number":74,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"fffc6b78_09a22f9b","line":71,"range":{"start_line":70,"start_character":72,"end_line":71,"end_character":7},"in_reply_to":"9f560f44_a4430f3f","updated":"2020-11-19 21:33:43.000000000","message":"Done","commit_id":"03e08352337eb23c718e29ce2e91ff4d7177ce41"},{"author":{"_account_id":5263,"name":"Jeremy Stanley","display_name":"fungi","email":"fungi@yuggoth.org","username":"fungi","status":"missing, presumed fed"},"change_message_id":"dbd55834c80538c4467b500f9de6046cf9ebaabc","unresolved":false,"context_lines":[{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs deliverables are not part of the coordinated release, and will not leverage"},{"line_number":71,"context_line":"the openstack/releases repository. Each SIG is responsible for its release"},{"line_number":72,"context_line":"management/tagging."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."},{"line_number":75,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"fffc6b78_c9ff8765","line":72,"updated":"2020-11-19 21:42:48.000000000","message":"Maybe add a parenthetical \"(if any)\" to the end of this sentence? The majority of SIGs don\u0027t need to tag releases of software, and probably won\u0027t even produce software, so it\u0027s relatively unlikely that this would ever come into play for them. Otherwise this section seems to imply that SIGs should be releasing things.","commit_id":"df7b89cffe4f999d89629fa35758cf0212a6b278"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"5432ffec06782039aa55e5a5863eace69920b9c2","unresolved":false,"context_lines":[{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs deliverables are not part of the coordinated release, and will not leverage"},{"line_number":71,"context_line":"the openstack/releases repository. Each SIG is responsible for its release"},{"line_number":72,"context_line":"management/tagging."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."},{"line_number":75,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"074b1de6_9b099a5e","line":72,"in_reply_to":"f1a98ec6_b5464a60","updated":"2020-12-03 15:45:22.000000000","message":"Done","commit_id":"df7b89cffe4f999d89629fa35758cf0212a6b278"},{"author":{"_account_id":8099,"name":"Graham Hayes","email":"gr@ham.ie","username":"graham"},"change_message_id":"5090c89bef3abd214c94c5e4c049f6648aa27f84","unresolved":true,"context_lines":[{"line_number":69,"context_line":"considered add-on software to the main \"OpenStack\" software releases. Therefore"},{"line_number":70,"context_line":"SIGs deliverables are not part of the coordinated release, and will not leverage"},{"line_number":71,"context_line":"the openstack/releases repository. Each SIG is responsible for its release"},{"line_number":72,"context_line":"management/tagging."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"You can check for `process to create a SIG`_ for creating a new SIG."},{"line_number":75,"context_line":""}],"source_content_type":"text/x-rst","patch_set":2,"id":"f1a98ec6_b5464a60","line":72,"in_reply_to":"fffc6b78_c9ff8765","updated":"2020-11-23 14:48:43.000000000","message":"\u003c Each SIG is responsible for its release\nmanagement/tagging\n\u003e If a SIG does release any tooling or software they are responsible for any release management/tagging needed.","commit_id":"df7b89cffe4f999d89629fa35758cf0212a6b278"}]}