)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"06fd94e54ae807c65307ffe426f4e7b00037c424","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4e3715f5_7deb8651","updated":"2022-05-25 19:35:34.000000000","message":"A few nits noted inline; content is fine.","commit_id":"f7a2e06d26c80902e4c94461297be283d06d5dbe"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"4d269420a12df4278d0a1b73119f965875068ede","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ee4d479c_8fa33e92","updated":"2022-05-26 16:10:54.000000000","message":"This looks consistent with what we have discussed.  Two wording nits in the case that another patch is pushed up.","commit_id":"36ff562d3172ad9492c0722640fe8ebc61ff6d29"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"511b32c5ca0f0983d3adaa7063fdbfe993074aba","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":2,"id":"065963ae_de37f995","updated":"2022-06-01 09:13:24.000000000","message":"This looks good to me. Just a small comment.","commit_id":"36ff562d3172ad9492c0722640fe8ebc61ff6d29"}],"resolutions/20220524-release-identification-process.rst":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"06fd94e54ae807c65307ffe426f4e7b00037c424","unresolved":true,"context_lines":[{"line_number":1,"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"2022-05-24 OpenStack Release identification process"},{"line_number":3,"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"After the Zed cycle, the OpenStack release naming process has been changed."}],"source_content_type":"text/x-rst","patch_set":1,"id":"1e929970_2fb6da01","line":2,"range":{"start_line":2,"start_character":21,"end_line":2,"end_character":22},"updated":"2022-05-25 19:35:34.000000000","message":"this is a super-nit, but if you keep this uppercase, you should probably do the same for I and P; if you want to keep those lowercase, then you should make this lowercase too","commit_id":"f7a2e06d26c80902e4c94461297be283d06d5dbe"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6f17c6f293f3500f70bfd3ee7faa388b574d357b","unresolved":false,"context_lines":[{"line_number":1,"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":2,"context_line":"2022-05-24 OpenStack Release identification process"},{"line_number":3,"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"After the Zed cycle, the OpenStack release naming process has been changed."}],"source_content_type":"text/x-rst","patch_set":1,"id":"72d36f08_0cc63bb9","line":2,"range":{"start_line":2,"start_character":21,"end_line":2,"end_character":22},"in_reply_to":"1e929970_2fb6da01","updated":"2022-05-25 21:43:33.000000000","message":"Done","commit_id":"f7a2e06d26c80902e4c94461297be283d06d5dbe"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"06fd94e54ae807c65307ffe426f4e7b00037c424","unresolved":true,"context_lines":[{"line_number":11,"context_line":""},{"line_number":12,"context_line":"* OpenStack release names selection criteria and the process will be handled"},{"line_number":13,"context_line":"  by the staff of the OpenInfra Foundation. Foundation staff will make sure"},{"line_number":14,"context_line":"  that it satisfies the OpenStack release team tooling requirements. The"},{"line_number":15,"context_line":"  OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":16,"context_line":"  Foundation staff."},{"line_number":17,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"8b8bc5f5_f108b6a5","line":14,"range":{"start_line":14,"start_character":7,"end_line":14,"end_character":19},"updated":"2022-05-25 19:35:34.000000000","message":"\"they satisfy\" (process has to produce the name in time to be useful to the release team, and the name has to work for what the release team will use it for).","commit_id":"f7a2e06d26c80902e4c94461297be283d06d5dbe"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6f17c6f293f3500f70bfd3ee7faa388b574d357b","unresolved":false,"context_lines":[{"line_number":11,"context_line":""},{"line_number":12,"context_line":"* OpenStack release names selection criteria and the process will be handled"},{"line_number":13,"context_line":"  by the staff of the OpenInfra Foundation. Foundation staff will make sure"},{"line_number":14,"context_line":"  that it satisfies the OpenStack release team tooling requirements. The"},{"line_number":15,"context_line":"  OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":16,"context_line":"  Foundation staff."},{"line_number":17,"context_line":""}],"source_content_type":"text/x-rst","patch_set":1,"id":"b9baaf53_3bb21938","line":14,"range":{"start_line":14,"start_character":7,"end_line":14,"end_character":19},"in_reply_to":"8b8bc5f5_f108b6a5","updated":"2022-05-25 21:43:33.000000000","message":"Done","commit_id":"f7a2e06d26c80902e4c94461297be283d06d5dbe"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"06fd94e54ae807c65307ffe426f4e7b00037c424","unresolved":true,"context_lines":[{"line_number":12,"context_line":"* OpenStack release names selection criteria and the process will be handled"},{"line_number":13,"context_line":"  by the staff of the OpenInfra Foundation. Foundation staff will make sure"},{"line_number":14,"context_line":"  that it satisfies the OpenStack release team tooling requirements. The"},{"line_number":15,"context_line":"  OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":16,"context_line":"  Foundation staff."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"6c0c42b4_02c73ead","line":15,"range":{"start_line":15,"start_character":29,"end_line":15,"end_character":31},"updated":"2022-05-25 19:35:34.000000000","message":"Dan suggested \"sign-off\" on the naming document, I think that\u0027s a good suggestion.","commit_id":"f7a2e06d26c80902e4c94461297be283d06d5dbe"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6f17c6f293f3500f70bfd3ee7faa388b574d357b","unresolved":false,"context_lines":[{"line_number":12,"context_line":"* OpenStack release names selection criteria and the process will be handled"},{"line_number":13,"context_line":"  by the staff of the OpenInfra Foundation. Foundation staff will make sure"},{"line_number":14,"context_line":"  that it satisfies the OpenStack release team tooling requirements. The"},{"line_number":15,"context_line":"  OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":16,"context_line":"  Foundation staff."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"}],"source_content_type":"text/x-rst","patch_set":1,"id":"1da1a80a_ed2f9763","line":15,"range":{"start_line":15,"start_character":29,"end_line":15,"end_character":31},"in_reply_to":"6c0c42b4_02c73ead","updated":"2022-05-25 21:43:33.000000000","message":"Done","commit_id":"f7a2e06d26c80902e4c94461297be283d06d5dbe"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"4d269420a12df4278d0a1b73119f965875068ede","unresolved":true,"context_lines":[{"line_number":3,"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\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d\u003d"},{"line_number":4,"context_line":""},{"line_number":5,"context_line":"After the Zed cycle, the OpenStack release naming process has been changed."},{"line_number":6,"context_line":"We introduced the release number as an identification code to release but"},{"line_number":7,"context_line":"will still have the release name especially to use for marketing usage."},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"* Each OpenStack release will have an identification code: “year”.”release"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2dfbd55b_b47f2a2f","line":6,"range":{"start_line":6,"start_character":58,"end_line":6,"end_character":69},"updated":"2022-05-26 16:10:54.000000000","message":"to a release ?","commit_id":"36ff562d3172ad9492c0722640fe8ebc61ff6d29"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"4d269420a12df4278d0a1b73119f965875068ede","unresolved":true,"context_lines":[{"line_number":19,"context_line":"  the release team will directly coordinate with the foundation staff."},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"* The release number will be used as the primary identifier in the development"},{"line_number":22,"context_line":"  cycle but the release name will also be used in some places. we will use"},{"line_number":23,"context_line":"  release number in the stable branch (Example: stable/2023.1), spec repo or"},{"line_number":24,"context_line":"  any other directory structure, testing tools etc. The release team can choose"},{"line_number":25,"context_line":"  either to continue using the release name or use number for release"},{"line_number":26,"context_line":"  tooling and milestone name."}],"source_content_type":"text/x-rst","patch_set":2,"id":"735f8d41_7ae12881","line":23,"range":{"start_line":22,"start_character":63,"end_line":23,"end_character":16},"updated":"2022-05-26 16:10:54.000000000","message":"We will use the release number","commit_id":"36ff562d3172ad9492c0722640fe8ebc61ff6d29"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"511b32c5ca0f0983d3adaa7063fdbfe993074aba","unresolved":true,"context_lines":[{"line_number":21,"context_line":"* The release number will be used as the primary identifier in the development"},{"line_number":22,"context_line":"  cycle but the release name will also be used in some places. we will use"},{"line_number":23,"context_line":"  release number in the stable branch (Example: stable/2023.1), spec repo or"},{"line_number":24,"context_line":"  any other directory structure, testing tools etc. The release team can choose"},{"line_number":25,"context_line":"  either to continue using the release name or use number for release"},{"line_number":26,"context_line":"  tooling and milestone name."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"All the changes mentioned in this resolution will be applied immediately after"},{"line_number":29,"context_line":"the Zed release cycle."}],"source_content_type":"text/x-rst","patch_set":2,"id":"914d4fc3_c0228d17","line":26,"range":{"start_line":24,"start_character":52,"end_line":26,"end_character":29},"updated":"2022-06-01 09:13:24.000000000","message":"Shouldn\u0027t this be clearly specified? Like use both. My concern is the confusion that can be created if the interpretation of the release team changes between releases.","commit_id":"36ff562d3172ad9492c0722640fe8ebc61ff6d29"}]}