)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":true,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"After the discussion in ML thread[1], gerrit[2], Foundation"},{"line_number":10,"context_line":"staff joined in TC meeting and we all agreed to give the release"},{"line_number":11,"context_line":"name handling to Foundation and TC will not be involve in that[3]."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Release name will be used for marketing purpose and relese tooling"},{"line_number":14,"context_line":"but we will use the release number as a primary identifier in the"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"e7781d5e_542c0ec7","line":11,"range":{"start_line":11,"start_character":47,"end_line":11,"end_character":54},"updated":"2022-05-25 19:26:49.000000000","message":"nit: involved","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":8,"context_line":""},{"line_number":9,"context_line":"After the discussion in ML thread[1], gerrit[2], Foundation"},{"line_number":10,"context_line":"staff joined in TC meeting and we all agreed to give the release"},{"line_number":11,"context_line":"name handling to Foundation and TC will not be involve in that[3]."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Release name will be used for marketing purpose and relese tooling"},{"line_number":14,"context_line":"but we will use the release number as a primary identifier in the"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"898623c1_98913a59","line":11,"range":{"start_line":11,"start_character":47,"end_line":11,"end_character":54},"in_reply_to":"e7781d5e_542c0ec7","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":true,"context_lines":[{"line_number":10,"context_line":"staff joined in TC meeting and we all agreed to give the release"},{"line_number":11,"context_line":"name handling to Foundation and TC will not be involve in that[3]."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Release name will be used for marketing purpose and relese tooling"},{"line_number":14,"context_line":"but we will use the release number as a primary identifier in the"},{"line_number":15,"context_line":"OpenStack development cycle. TC had another call[4] to discuss about"},{"line_number":16,"context_line":"the details of where to use releae name and number and passed the"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"713dd162_b80581e6","line":13,"range":{"start_line":13,"start_character":52,"end_line":13,"end_character":58},"updated":"2022-05-25 19:26:49.000000000","message":"release","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":10,"context_line":"staff joined in TC meeting and we all agreed to give the release"},{"line_number":11,"context_line":"name handling to Foundation and TC will not be involve in that[3]."},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"Release name will be used for marketing purpose and relese tooling"},{"line_number":14,"context_line":"but we will use the release number as a primary identifier in the"},{"line_number":15,"context_line":"OpenStack development cycle. TC had another call[4] to discuss about"},{"line_number":16,"context_line":"the details of where to use releae name and number and passed the"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":4,"id":"d432a25a_747b4f96","line":13,"range":{"start_line":13,"start_character":52,"end_line":13,"end_character":58},"in_reply_to":"713dd162_b80581e6","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"6522ada093197dec3ad1c58842ddf2ebc1200045","unresolved":true,"context_lines":[{"line_number":13,"context_line":"Release name will be used for marketing purpose and release tooling"},{"line_number":14,"context_line":"but we will use the release number as a primary identifier in the"},{"line_number":15,"context_line":"OpenStack development cycle. TC had another call[4] to discuss about"},{"line_number":16,"context_line":"the details of where to use releae name and number and passed the"},{"line_number":17,"context_line":"resolution"},{"line_number":18,"context_line":"- https://review.opendev.org/c/openstack/governance/+/843214"},{"line_number":19,"context_line":""}],"source_content_type":"text/x-gerrit-commit-message","patch_set":5,"id":"df2ed15d_71650aad","line":16,"range":{"start_line":16,"start_character":28,"end_line":16,"end_character":34},"updated":"2022-05-27 09:02:53.000000000","message":"nitty nit: release","commit_id":"d29da1b7de593228a5d32d1fd905841c4de4b40c"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"af19cc2a5d6988f6b42b8dc9107981d4bf1bf16c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"7981d58c_29c7106d","updated":"2022-05-18 14:12:08.000000000","message":"I think we can distinguish between the process and the criteria; see comment inline.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"1d57898ab7276606cfb35c647082fc28bf07b4d6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"098ad81c_c61ccb3a","updated":"2022-05-16 19:44:25.000000000","message":"Looks like this needs some fine-tuning; will re-vote after the TC meeting this week.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9b6b5e37e0e5b5bbfcd79dc6337ce5b48e2812d2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c001a518_a5980252","updated":"2022-05-16 20:48:02.000000000","message":"This patch goes beyond what I thought had happened at last week\u0027s meeting in two ways.\n\n1. I think this revision should be closer to Belmiro\u0027s original proposal [0], the point of which was basically just that since we\u0027re repeating the alphabet, we need additional info to simply the name to determine where a release falls in the complete ordering of releases.  We had been considering dropping the name completely, but instead, we agreed that the Foundation should select the release name.  So now we\u0027re back to identifier + name.  (I didn\u0027t think we agreed to any changes in tooling, etc., and since we\u0027re back to identifier + name, I don\u0027t think any such changes are necessary?)\n\n2. While we want to give the naming selection over to the Foundation, I didn\u0027t think we were giving them control over the naming criteria (that is, I was expecting that they would continue the alphabetical ordering, 26 chars of ISO basic Latin, maxlen 10 chars, no repetition of a name over different iterations of the alphabet) that we\u0027ve built a bunch of tooling and practice around.\n\nSuggestions inline for some clarifications.\n\n[0] https://opendev.org/openstack/governance/commit/aaa531c75d76d6996dccd6dc373e603ab9a5057a","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"b03672a7dbdb9646702319d79a98a11f525cf542","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"0c302a47_5f36b23f","updated":"2022-05-14 16:53:04.000000000","message":"This summarizes what we agreed to.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a53ac3a269cd7d6932cc0fdc71678c9552c3c240","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"72df7436_3b083a40","in_reply_to":"c001a518_a5980252","updated":"2022-05-17 01:29:07.000000000","message":"1st part we will discuss in next meeting. This has not been discussed in a clear way.\n\n2nd part, this is what we agreed in meeting that TC will not be involved and let Foundation own the process as well as execution. TC owning process and just asking Foundation to execute it mixup the ownership of this activity.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"3c30ef50_4b80db66","updated":"2022-05-25 19:26:49.000000000","message":"Content is good, a few typos and grammar things noted inline.","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e0c77883cd59a9ca6b55d4f6a845b8e86087e4e5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"85cab32b_21a2e051","updated":"2022-05-25 19:17:51.000000000","message":"I am cool with this as-is, but some grammar suggestions.","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"3bc6186063da130ef7de8d8632b338b2b9b971bb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"e7c3129f_2dca878d","updated":"2022-05-26 16:13:28.000000000","message":"Looks good.  Thank you!","commit_id":"d29da1b7de593228a5d32d1fd905841c4de4b40c"}],"reference/release-naming.rst":[{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9b6b5e37e0e5b5bbfcd79dc6337ce5b48e2812d2","unresolved":true,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* OpenStack 2023.1 Axxxx"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Where \"2023\" is the year of the release, \"1\" represents the first release"},{"line_number":16,"context_line":"of the year and \"Axxxx\" is the release name following the release name rules."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Other examples:"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"* OpenStack 2023.2 Bxxxx"},{"line_number":21,"context_line":"* OpenStack 2024.1 Cxxxx"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"With this release identification schema we get an easy and sustainable"},{"line_number":24,"context_line":"approach to identify different OpenStack releases without dealing with the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"8e9f5fd9_6c770de3","side":"PARENT","line":21,"range":{"start_line":13,"start_character":0,"end_line":21,"end_character":24},"updated":"2022-05-16 20:48:02.000000000","message":"I think you should restore all this (though in line 16, you may want to say \"release name criteria\" to be consistent with later in the document).","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":false,"context_lines":[{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example:"},{"line_number":12,"context_line":""},{"line_number":13,"context_line":"* OpenStack 2023.1 Axxxx"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Where \"2023\" is the year of the release, \"1\" represents the first release"},{"line_number":16,"context_line":"of the year and \"Axxxx\" is the release name following the release name rules."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Other examples:"},{"line_number":19,"context_line":""},{"line_number":20,"context_line":"* OpenStack 2023.2 Bxxxx"},{"line_number":21,"context_line":"* OpenStack 2024.1 Cxxxx"},{"line_number":22,"context_line":""},{"line_number":23,"context_line":"With this release identification schema we get an easy and sustainable"},{"line_number":24,"context_line":"approach to identify different OpenStack releases without dealing with the"}],"source_content_type":"text/x-rst","patch_set":2,"id":"660dc396_8c703a73","side":"PARENT","line":21,"range":{"start_line":13,"start_character":0,"end_line":21,"end_character":24},"in_reply_to":"8e9f5fd9_6c770de3","updated":"2022-05-25 19:26:49.000000000","message":"Done","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9b6b5e37e0e5b5bbfcd79dc6337ce5b48e2812d2","unresolved":true,"context_lines":[{"line_number":44,"context_line":"Release Naming Process"},{"line_number":45,"context_line":"----------------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. Anyone may propose a name that matches the `Release Name"},{"line_number":48,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":49,"context_line":"   OpenStack wiki."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":52,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":53,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":56,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"},{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"}],"source_content_type":"text/x-rst","patch_set":2,"id":"e892b22b_69883e1d","side":"PARENT","line":58,"range":{"start_line":47,"start_character":0,"end_line":58,"end_character":64},"updated":"2022-05-16 20:48:02.000000000","message":"I suggest restoring the \"Release Naming Process\" section, but replace these 3 points with: \"Release names are selected by the OpenDev Foundation following the criteria set out below.  It is expected that the Foundation will make the release name available to the OpenStack community by week R-11 of the prior release\u0027s development cycle.\"","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":false,"context_lines":[{"line_number":44,"context_line":"Release Naming Process"},{"line_number":45,"context_line":"----------------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. Anyone may propose a name that matches the `Release Name"},{"line_number":48,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":49,"context_line":"   OpenStack wiki."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":52,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":53,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":56,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"},{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"}],"source_content_type":"text/x-rst","patch_set":2,"id":"94883499_8b68b520","side":"PARENT","line":58,"range":{"start_line":47,"start_character":0,"end_line":58,"end_character":64},"in_reply_to":"4241a7c3_3fd0ddb6","updated":"2022-05-25 19:26:49.000000000","message":"Ack","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a53ac3a269cd7d6932cc0fdc71678c9552c3c240","unresolved":true,"context_lines":[{"line_number":44,"context_line":"Release Naming Process"},{"line_number":45,"context_line":"----------------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. Anyone may propose a name that matches the `Release Name"},{"line_number":48,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":49,"context_line":"   OpenStack wiki."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":52,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":53,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":56,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"},{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"}],"source_content_type":"text/x-rst","patch_set":2,"id":"f6a1e758_7d9c6326","side":"PARENT","line":58,"range":{"start_line":47,"start_character":0,"end_line":58,"end_character":64},"in_reply_to":"e892b22b_69883e1d","updated":"2022-05-17 01:29:07.000000000","message":"that is what we discussed in meeting that TC will not be involved in the release name and it will be handled by the foundation. \u0027Not involved\u0027 means we as TC should not define or control the criteria instead foundation should own that. They can use this process we we used till now or define new one. TC owning the process but asking foundation to execute it does not make any difference than what issue we are facing currently. It is completly shifting the release name things to Foundation.\n\nWe should let Foundation to own the process as well as the execution.","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"af19cc2a5d6988f6b42b8dc9107981d4bf1bf16c","unresolved":true,"context_lines":[{"line_number":44,"context_line":"Release Naming Process"},{"line_number":45,"context_line":"----------------------"},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. Anyone may propose a name that matches the `Release Name"},{"line_number":48,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":49,"context_line":"   OpenStack wiki."},{"line_number":50,"context_line":""},{"line_number":51,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":52,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":53,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":54,"context_line":""},{"line_number":55,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":56,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"},{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"}],"source_content_type":"text/x-rst","patch_set":2,"id":"4241a7c3_3fd0ddb6","side":"PARENT","line":58,"range":{"start_line":47,"start_character":0,"end_line":58,"end_character":64},"in_reply_to":"f6a1e758_7d9c6326","updated":"2022-05-18 14:12:08.000000000","message":"I think we can make a distinction between the process of determining the name, vs. the syntactic criteria of what the name should look like.  What I thought we were saying to the Foundation is that we want them to deliver to us a sequence of at most 10 chars from ISO basic latin that doesn\u0027t repeat a name that has already been used, and whose first letter follows immediately alphabetically from the previous name (modulo A-Z).  And we can say that we need it by R-11.  How they come up with it, or what it means semantically, is entirely up to them (i.e., they own the process).","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9b6b5e37e0e5b5bbfcd79dc6337ce5b48e2812d2","unresolved":true,"context_lines":[{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"},{"line_number":62,"context_line":"---------------------"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"The following rules are designed to provide some consistency in the"},{"line_number":65,"context_line":"pattern used to select release names, provide a fun challenge in"},{"line_number":66,"context_line":"finding names that meet the criteria, and prevent unwieldy names from"},{"line_number":67,"context_line":"being chosen."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"#. Each release name must start with the letter of the ISO basic Latin"},{"line_number":70,"context_line":"   alphabet following the initial letter of the previous release,"},{"line_number":71,"context_line":"   starting with the initial release of \"Austin\".  After \"Z\", the next"},{"line_number":72,"context_line":"   name should start with \"A\" again."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"#. A release name can\u0027t be repeated between different iterations of the"},{"line_number":75,"context_line":"   alphabet."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"#. The name must be composed only of the 26 characters of the ISO"},{"line_number":78,"context_line":"   basic Latin alphabet.  Names which can be transliterated into this"},{"line_number":79,"context_line":"   character set are also acceptable."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"#. The name must be a single word with a maximum length of 10 characters."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Polls"},{"line_number":84,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c3f1b126_6f5475e0","side":"PARENT","line":81,"range":{"start_line":60,"start_character":0,"end_line":81,"end_character":73},"updated":"2022-05-16 20:48:02.000000000","message":"I think we should restore this \"Release Name Criteria\" section.  We\u0027ve asked the Foundation to handle assigning the release name, but that doesn\u0027t mean anything goes ... we need to be clear to the Foundation that we are asking them to select a name within these parameters.","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"af19cc2a5d6988f6b42b8dc9107981d4bf1bf16c","unresolved":true,"context_lines":[{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"},{"line_number":62,"context_line":"---------------------"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"The following rules are designed to provide some consistency in the"},{"line_number":65,"context_line":"pattern used to select release names, provide a fun challenge in"},{"line_number":66,"context_line":"finding names that meet the criteria, and prevent unwieldy names from"},{"line_number":67,"context_line":"being chosen."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"#. Each release name must start with the letter of the ISO basic Latin"},{"line_number":70,"context_line":"   alphabet following the initial letter of the previous release,"},{"line_number":71,"context_line":"   starting with the initial release of \"Austin\".  After \"Z\", the next"},{"line_number":72,"context_line":"   name should start with \"A\" again."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"#. A release name can\u0027t be repeated between different iterations of the"},{"line_number":75,"context_line":"   alphabet."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"#. The name must be composed only of the 26 characters of the ISO"},{"line_number":78,"context_line":"   basic Latin alphabet.  Names which can be transliterated into this"},{"line_number":79,"context_line":"   character set are also acceptable."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"#. The name must be a single word with a maximum length of 10 characters."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Polls"},{"line_number":84,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ff86703e_84a9fdd9","side":"PARENT","line":81,"range":{"start_line":60,"start_character":0,"end_line":81,"end_character":73},"in_reply_to":"bfb831c2_ad4b6218","updated":"2022-05-18 14:12:08.000000000","message":"ditto also.","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a53ac3a269cd7d6932cc0fdc71678c9552c3c240","unresolved":true,"context_lines":[{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"},{"line_number":62,"context_line":"---------------------"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"The following rules are designed to provide some consistency in the"},{"line_number":65,"context_line":"pattern used to select release names, provide a fun challenge in"},{"line_number":66,"context_line":"finding names that meet the criteria, and prevent unwieldy names from"},{"line_number":67,"context_line":"being chosen."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"#. Each release name must start with the letter of the ISO basic Latin"},{"line_number":70,"context_line":"   alphabet following the initial letter of the previous release,"},{"line_number":71,"context_line":"   starting with the initial release of \"Austin\".  After \"Z\", the next"},{"line_number":72,"context_line":"   name should start with \"A\" again."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"#. A release name can\u0027t be repeated between different iterations of the"},{"line_number":75,"context_line":"   alphabet."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"#. The name must be composed only of the 26 characters of the ISO"},{"line_number":78,"context_line":"   basic Latin alphabet.  Names which can be transliterated into this"},{"line_number":79,"context_line":"   character set are also acceptable."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"#. The name must be a single word with a maximum length of 10 characters."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Polls"},{"line_number":84,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bfb831c2_ad4b6218","side":"PARENT","line":81,"range":{"start_line":60,"start_character":0,"end_line":81,"end_character":73},"in_reply_to":"c3f1b126_6f5475e0","updated":"2022-05-17 01:29:07.000000000","message":"ditto, above comment.","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":false,"context_lines":[{"line_number":57,"context_line":"   down the ranked list of Condorcet results until a name without a"},{"line_number":58,"context_line":"   trademark conflict is found.  This will be the selected name."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":""},{"line_number":61,"context_line":"Release Name Criteria"},{"line_number":62,"context_line":"---------------------"},{"line_number":63,"context_line":""},{"line_number":64,"context_line":"The following rules are designed to provide some consistency in the"},{"line_number":65,"context_line":"pattern used to select release names, provide a fun challenge in"},{"line_number":66,"context_line":"finding names that meet the criteria, and prevent unwieldy names from"},{"line_number":67,"context_line":"being chosen."},{"line_number":68,"context_line":""},{"line_number":69,"context_line":"#. Each release name must start with the letter of the ISO basic Latin"},{"line_number":70,"context_line":"   alphabet following the initial letter of the previous release,"},{"line_number":71,"context_line":"   starting with the initial release of \"Austin\".  After \"Z\", the next"},{"line_number":72,"context_line":"   name should start with \"A\" again."},{"line_number":73,"context_line":""},{"line_number":74,"context_line":"#. A release name can\u0027t be repeated between different iterations of the"},{"line_number":75,"context_line":"   alphabet."},{"line_number":76,"context_line":""},{"line_number":77,"context_line":"#. The name must be composed only of the 26 characters of the ISO"},{"line_number":78,"context_line":"   basic Latin alphabet.  Names which can be transliterated into this"},{"line_number":79,"context_line":"   character set are also acceptable."},{"line_number":80,"context_line":""},{"line_number":81,"context_line":"#. The name must be a single word with a maximum length of 10 characters."},{"line_number":82,"context_line":""},{"line_number":83,"context_line":"Polls"},{"line_number":84,"context_line":"-----"}],"source_content_type":"text/x-rst","patch_set":2,"id":"a2fd29c7_7cb8ad5d","side":"PARENT","line":81,"range":{"start_line":60,"start_character":0,"end_line":81,"end_character":73},"in_reply_to":"ff86703e_84a9fdd9","updated":"2022-05-25 19:26:49.000000000","message":"Ack","commit_id":"353dfb7b62bdd88bbfaf05fddadc1e673b06a9ee"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"5b1505ad864c4f9a561658c2f75be2ffd0198992","unresolved":true,"context_lines":[{"line_number":24,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":25,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"The release number will be used as the primary identifier in our release"},{"line_number":28,"context_line":"scheduling, automated processes, directory structure etc."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"faf94646_a565f9a7","line":28,"range":{"start_line":27,"start_character":0,"end_line":28,"end_character":57},"updated":"2022-05-16 15:15:03.000000000","message":"This conflicts with Thierry\u0027s answer below, about the release\u0027s team preference to keep branches/releases with the release name.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"a53ac3a269cd7d6932cc0fdc71678c9552c3c240","unresolved":true,"context_lines":[{"line_number":24,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":25,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"The release number will be used as the primary identifier in our release"},{"line_number":28,"context_line":"scheduling, automated processes, directory structure etc."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c2c4e8ca_6561a1e7","line":28,"range":{"start_line":27,"start_character":0,"end_line":28,"end_character":57},"in_reply_to":"0233788b_048f14dd","updated":"2022-05-17 01:29:07.000000000","message":"you are right. We did not discuss that part and i have added part for TC next meeting- https://wiki.openstack.org/wiki/Meetings/TechnicalCommittee#Next_Meeting","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":false,"context_lines":[{"line_number":24,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":25,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"The release number will be used as the primary identifier in our release"},{"line_number":28,"context_line":"scheduling, automated processes, directory structure etc."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3308b67d_193c22d5","line":28,"range":{"start_line":27,"start_character":0,"end_line":28,"end_character":57},"in_reply_to":"c2c4e8ca_6561a1e7","updated":"2022-05-25 19:26:49.000000000","message":"Ack","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9b6b5e37e0e5b5bbfcd79dc6337ce5b48e2812d2","unresolved":true,"context_lines":[{"line_number":24,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":25,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":26,"context_line":""},{"line_number":27,"context_line":"The release number will be used as the primary identifier in our release"},{"line_number":28,"context_line":"scheduling, automated processes, directory structure etc."},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"}],"source_content_type":"text/x-rst","patch_set":2,"id":"0233788b_048f14dd","line":28,"range":{"start_line":27,"start_character":0,"end_line":28,"end_character":57},"in_reply_to":"faf94646_a565f9a7","updated":"2022-05-16 20:48:02.000000000","message":"The above goes beyond what I thought happened at the meeting last week.\n\nThe proposal floated on the mailing list was to drop the name completely and using only the identifier, but the Foundation proposed doing the work of selecting an appropriate name for us, and we said that was OK.\n\nSo I don\u0027t see why we need to replace Belmiro\u0027s original language of \"The release identification schema doesn\u0027t replace the release name.  It\u0027s just an unambiguous way to identify OpenStack releases.\"  In other words, I think this update to the document should just describe the new selection process, but should not prescribe any other changes about tooling, etc.\n\n(Looking back over the meeting log[*], Jeremy did say \"i think it\u0027s also, separately, a good idea to continue with the currently published versioning plan to use release numbers as primary identifiers in our scheduling and automated processes, leaving the cycle names as more of a marketing feature which isn\u0027t integral to most of the schedule\", but I\u0027m not sure exactly what currently published versioning plan he was referring to.  I\u0027ve only been on the TC a short while, so it may have happened before my time.)\n\n[*] https://meetings.opendev.org/meetings/tc/2022/tc.2022-05-12-15.00.log.html#l-332","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":8313,"name":"Lajos Katona","display_name":"lajoskatona","email":"katonalala@gmail.com","username":"elajkat","status":"Ericsson Software Technology"},"change_message_id":"4a77ab59d342f0367c028f43f07a0de700691ab1","unresolved":true,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"bcc4a849_052f16ae","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"updated":"2022-05-16 07:23:53.000000000","message":"A dumb question: do we keep the names for branches? Or we will have branch names like stable/2023_2 ?","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"ae2cf2f36b57533ad7249e1a61e78b6ab631a626","unresolved":true,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2b75511a_bb1fb10d","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"in_reply_to":"2246aba8_3ffd4789","updated":"2022-05-16 16:30:07.000000000","message":"I think I am mixing two things here, my bad. \n\nTill now, we concluded who will handle the release name and no objection to giving it to Foundation. but we still did not agree or even I will say discuss \"Which one (release name or number) and how to use them in the development process\". I will add the latter one to the TC meeting agenda with the release team or some ad-hoc meetings.\n\nOne thing clear is we need to make release numbers primary identifiers otherwise they will go unused.\n\nThere are a few options:\n\nOption 1 (this proposal): Whether we want to keep the release name only for the marketing process. And only use the release number for the development process.\n\nOption 2 (Current process): Use release names as it is they are used currently in the market as well as in the development process. Drop the release number as they might be just mentioned in this document and not used anywhere else.\n\nOption 3 (new proposal): Use both release numbers as well names in the development process as well as on the marketing side. But the Primary identifier will be the release number. But might be complex to know where to use which one.\n\nRelease numbers we added earlier for the reason mentioned in L23. If we go with the 2nd approach then the question is how we will make use of numbers and people (develops as well as users) to remember this as the primary identifier of OpenStack releases. \n\nOption 1 will look like:\n\n* Release schedule page:\n  ** title: OpenStack 2023.1\n  ** milestone as \"2023.1-1 milestone\"\n* stable branches: stable/2023.1\n* spec folder: specs/2023_1/approved\n\nOption 3 will look like (or maybe any other better way but keep the release number as the primary identifier):\n \n* Release schedule page:\n  ** title: OpenStack 2023.1 (Aardvark) \n  ** milestone is ok to mention either \"aardvark-1 milestone\" or \"2023.1-1 \n     milestone\". latter will be more aligned to use release number in the \n     development process.\n* stable branches: stable/2023.1\n* spec folder: specs/2023_1/approved or specs/aardvark/approved\n\nopinion?","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"4a9391db1f54059d72626d9c9cbed6846bf29c36","unresolved":true,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"80116fef_152c81d8","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"in_reply_to":"2b75511a_bb1fb10d","updated":"2022-05-16 16:40:49.000000000","message":"To be clear, the resolution was about the release identification -- clearly the release itself should be primarily identified as its number (\"2023.1\"). The question here is whether the *development cycle* should be primarily identified under the name (\"the Aardvark development cycle\") or the number. The release team finds 2023.1-2 and 2023.2-1 a lot less clear to communicate than Aardvark-2 and Brew-1, which is why it is our preference to communicate about development milestones using names. Stable branches are somewhere in the middle (created at the end of the cycle) -- we can make it work with names or numbers.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":16643,"name":"Goutham Pacha Ravi","email":"gouthampravi@gmail.com","username":"gouthamr"},"change_message_id":"bf795aba62bf8eaf87c5f4b3ddf167c20b07620c","unresolved":true,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"ab6aeb0b_f1cf189d","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"in_reply_to":"43d2b5a9_28856e9f","updated":"2022-05-16 14:32:42.000000000","message":"+1","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"9b6b5e37e0e5b5bbfcd79dc6337ce5b48e2812d2","unresolved":true,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c9ec459d_dc1c5165","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"in_reply_to":"80116fef_152c81d8","updated":"2022-05-16 20:48:02.000000000","message":"I suggest replacing lines 33-36 with \"Each OpenStack development cycle has a code-name that is selected by the OpenDev Foundation following the process and criteria set out below.  As described in the \"Release Identification\" section above, this name is frequently used in combination with the version number to refer to the release at the end of the cycle.\"","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":16465,"name":"Kristi Nikolla","email":"knikolla@bu.edu","username":"knikolla"},"change_message_id":"5b1505ad864c4f9a561658c2f75be2ffd0198992","unresolved":true,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"2246aba8_3ffd4789","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"in_reply_to":"ab6aeb0b_f1cf189d","updated":"2022-05-16 15:15:03.000000000","message":"This document needs to be update to reflect the above ^ as the current wording conflicts with that.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"2a6616fd79b301fc46ff387d4ea4aabb30221ea4","unresolved":true,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"43d2b5a9_28856e9f","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"in_reply_to":"bcc4a849_052f16ae","updated":"2022-05-16 08:51:16.000000000","message":"That\u0027s an excellent question... We discussed it during the release team meeting last Friday.\n\nThe release team will continue to use the name in development cycle names (\"the Aardvark cycle\") and release milestone names (think: \"aardvark-1 milestone\" instead of \"2023.1-1 milestone\"). In order to minimize release process changes, our preference would be to keep using the name in the branches as well (stable/aardvark rather than stable/2023.1)... But we could also make numbers work if that\u0027s a requirement for branch names.","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":false,"context_lines":[{"line_number":30,"context_line":"Release Name"},{"line_number":31,"context_line":"------------"},{"line_number":32,"context_line":""},{"line_number":33,"context_line":"We will continue with the release name for the marketing usage. OpenStack"},{"line_number":34,"context_line":"release names are chosen/handled by the staff of the OpenInfra Foundation."},{"line_number":35,"context_line":"The release team or any other team that requires a release name to use in"},{"line_number":36,"context_line":"their documents can directly reach out to the OpenInfra Foundation."},{"line_number":37,"context_line":""},{"line_number":38,"context_line":""},{"line_number":39,"context_line":"Release name selection History"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3d47f06e_8a76912e","line":36,"range":{"start_line":33,"start_character":0,"end_line":36,"end_character":67},"in_reply_to":"c9ec459d_dc1c5165","updated":"2022-05-25 19:26:49.000000000","message":"Done","commit_id":"97fd8a0880234658c0cb99e6d415fdbc25ae2f33"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":true,"context_lines":[{"line_number":13,"context_line":"* OpenStack 2023.1 Axxxx"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Where \"2023\" is the year of the release, \"1\" represents the first release"},{"line_number":16,"context_line":"of the year and \"Axxxx\" is the release name following the release name rules."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Other examples:"},{"line_number":19,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"421dae8c_6ed13f35","line":16,"range":{"start_line":16,"start_character":44,"end_line":16,"end_character":76},"updated":"2022-05-25 19:26:49.000000000","message":"Maybe \"selected by the Foundation\" (or just end the sentence at \"release name\").","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":13,"context_line":"* OpenStack 2023.1 Axxxx"},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"Where \"2023\" is the year of the release, \"1\" represents the first release"},{"line_number":16,"context_line":"of the year and \"Axxxx\" is the release name following the release name rules."},{"line_number":17,"context_line":""},{"line_number":18,"context_line":"Other examples:"},{"line_number":19,"context_line":""}],"source_content_type":"text/x-rst","patch_set":4,"id":"23089bec_db5b7f84","line":16,"range":{"start_line":16,"start_character":44,"end_line":16,"end_character":76},"in_reply_to":"421dae8c_6ed13f35","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e0c77883cd59a9ca6b55d4f6a845b8e86087e4e5","unresolved":true,"context_lines":[{"line_number":52,"context_line":"  Foundation."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."}],"source_content_type":"text/x-rst","patch_set":4,"id":"27410b2c_767915bd","line":55,"range":{"start_line":55,"start_character":2,"end_line":55,"end_character":9},"updated":"2022-05-25 19:17:51.000000000","message":"\"satisfies\"","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e0c77883cd59a9ca6b55d4f6a845b8e86087e4e5","unresolved":true,"context_lines":[{"line_number":52,"context_line":"  Foundation."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."}],"source_content_type":"text/x-rst","patch_set":4,"id":"2c696e5c_154fd3a5","line":55,"range":{"start_line":55,"start_character":32,"end_line":55,"end_character":36},"updated":"2022-05-25 19:17:51.000000000","message":"\"team\u0027s\"","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":true,"context_lines":[{"line_number":52,"context_line":"  Foundation."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."}],"source_content_type":"text/x-rst","patch_set":4,"id":"573bd4bb_4ebb03b2","line":55,"range":{"start_line":55,"start_character":2,"end_line":55,"end_character":9},"in_reply_to":"27410b2c_767915bd","updated":"2022-05-25 19:26:49.000000000","message":"or, \"they satisfy\" since we\u0027re talking about criteria and process","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  Foundation."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."}],"source_content_type":"text/x-rst","patch_set":4,"id":"74de66e7_19039466","line":55,"range":{"start_line":55,"start_character":32,"end_line":55,"end_character":36},"in_reply_to":"2c696e5c_154fd3a5","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":52,"context_line":"  Foundation."},{"line_number":53,"context_line":""},{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."}],"source_content_type":"text/x-rst","patch_set":4,"id":"7cbc3587_ec399862","line":55,"range":{"start_line":55,"start_character":2,"end_line":55,"end_character":9},"in_reply_to":"573bd4bb_4ebb03b2","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e0c77883cd59a9ca6b55d4f6a845b8e86087e4e5","unresolved":true,"context_lines":[{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"a3354d01_411dcf4c","line":57,"range":{"start_line":57,"start_character":33,"end_line":57,"end_character":35},"updated":"2022-05-25 19:17:51.000000000","message":"To avoid confusion about any voting in gerrit, it might be best to change this to \"sign-off\"","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":true,"context_lines":[{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"c427b902_dc24b6b4","line":57,"range":{"start_line":57,"start_character":33,"end_line":57,"end_character":35},"in_reply_to":"a3354d01_411dcf4c","updated":"2022-05-25 19:26:49.000000000","message":"Agree with Dan; same change should be made in the resolution.","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":54,"context_line":"* Foundation staff will define the naming criteria and process but make sure it"},{"line_number":55,"context_line":"  satisfy the OpenStack release team tooling requirements."},{"line_number":56,"context_line":""},{"line_number":57,"context_line":"* The OpenStack release team PTL +1 is needed on naming criteria defined by the"},{"line_number":58,"context_line":"  Foundation staff."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"}],"source_content_type":"text/x-rst","patch_set":4,"id":"34a7fd93_c98a7d87","line":57,"range":{"start_line":57,"start_character":33,"end_line":57,"end_character":35},"in_reply_to":"c427b902_dc24b6b4","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"e0c77883cd59a9ca6b55d4f6a845b8e86087e4e5","unresolved":true,"context_lines":[{"line_number":58,"context_line":"  Foundation staff."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"},{"line_number":61,"context_line":"  the release team can directly coordinate with the foundation staff."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Release name selection History"},{"line_number":64,"context_line":"------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"2b056066_ab54b921","line":61,"range":{"start_line":61,"start_character":19,"end_line":61,"end_character":22},"updated":"2022-05-25 19:17:51.000000000","message":"\"will\"","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":58,"context_line":"  Foundation staff."},{"line_number":59,"context_line":""},{"line_number":60,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"},{"line_number":61,"context_line":"  the release team can directly coordinate with the foundation staff."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Release name selection History"},{"line_number":64,"context_line":"------------------------------"}],"source_content_type":"text/x-rst","patch_set":4,"id":"c39ac0f5_0f58d2f1","line":61,"range":{"start_line":61,"start_character":19,"end_line":61,"end_character":22},"in_reply_to":"2b056066_ab54b921","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":true,"context_lines":[{"line_number":60,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"},{"line_number":61,"context_line":"  the release team can directly coordinate with the foundation staff."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Release name selection History"},{"line_number":64,"context_line":"------------------------------"},{"line_number":65,"context_line":""},{"line_number":66,"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\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":4,"id":"f35ba638_c5591345","line":63,"range":{"start_line":63,"start_character":0,"end_line":63,"end_character":30},"updated":"2022-05-25 19:26:49.000000000","message":"nit: Release Name Selection History (to be consistent with the other section headings)","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":60,"context_line":"* The OpenStack Technical Committee will not be involved in the process,"},{"line_number":61,"context_line":"  the release team can directly coordinate with the foundation staff."},{"line_number":62,"context_line":""},{"line_number":63,"context_line":"Release name selection History"},{"line_number":64,"context_line":"------------------------------"},{"line_number":65,"context_line":""},{"line_number":66,"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\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":4,"id":"3b45ba6d_3c934b00","line":63,"range":{"start_line":63,"start_character":0,"end_line":63,"end_character":30},"in_reply_to":"f35ba638_c5591345","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"ea62ab66176223b4600b0058702e1c84a50a1ac5","unresolved":true,"context_lines":[{"line_number":81,"context_line":"Y_       Ghanshyam Mann  2021-05-13        2021-06-10  2021-06-17  N/A"},{"line_number":82,"context_line":"Z_       Ghanshyam Mann  2022-01-11        2022-01-25  2022-02-01  N/A"},{"line_number":83,"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\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":84,"context_line":""},{"line_number":85,"context_line":".. [*] Starting with the W release, the naming criteria changed from referring"},{"line_number":86,"context_line":"   to the physical or human geography of the region encompassing the location"},{"line_number":87,"context_line":"   of the OpenStack Summit, to any name proposed by the community that starts"}],"source_content_type":"text/x-rst","patch_set":4,"id":"310d3cf2_3de60efe","line":84,"updated":"2022-05-25 19:26:49.000000000","message":"I suggest adding a sentence after the table, something like:\n\nThe Z release is the final release for which the OpenStack Technical Committee was involved in the selection of the release name.\n\n(It closes the document, and also would be helpful to people who are just looking at the table and haven\u0027t read the entire document.)","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"2429dfbbd282e1dd05e5c01d124315b5a46d5c3b","unresolved":false,"context_lines":[{"line_number":81,"context_line":"Y_       Ghanshyam Mann  2021-05-13        2021-06-10  2021-06-17  N/A"},{"line_number":82,"context_line":"Z_       Ghanshyam Mann  2022-01-11        2022-01-25  2022-02-01  N/A"},{"line_number":83,"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\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":84,"context_line":""},{"line_number":85,"context_line":".. [*] Starting with the W release, the naming criteria changed from referring"},{"line_number":86,"context_line":"   to the physical or human geography of the region encompassing the location"},{"line_number":87,"context_line":"   of the OpenStack Summit, to any name proposed by the community that starts"}],"source_content_type":"text/x-rst","patch_set":4,"id":"5a6b4633_720beab1","line":84,"in_reply_to":"310d3cf2_3de60efe","updated":"2022-05-25 22:11:38.000000000","message":"Done","commit_id":"45e6f2e990a34c56dd1842db15744c309a40ff1f"}]}