)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"b99f71de8cbf3b78ca80a45d71a1c26fbe7ebba9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"eaf78c23_0e23de62","updated":"2022-02-17 16:22:25.000000000","message":"Agree with the nits, but +1 otherwise","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"aa6b207e1db815ef677f20daf887efd01de08c71","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"d28804d4_fd12d431","updated":"2022-02-17 16:32:18.000000000","message":"If the plan is to say \u003c\u003c OpenStack 2022.2 (\"Aardvark\") \u003e\u003e and the name of the series can continue to be used in the release tooling (in particular in the stable branch name) I have far less concerns.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"ca6d5777f7a0b194beb1e81e809bcb22a7057e34","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"c680a0e6_13ce5e84","updated":"2022-02-17 17:22:00.000000000","message":"Overall I am +1 on the intention.  Think the nits need to be addressed.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"6cd9b96dfaee3f3f3ed524f7659d07d9a55ef933","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"cac5ef89_f581fa25","updated":"2022-02-16 16:04:17.000000000","message":"RV+1 otherwise","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"ef6ac684f1077850392662ebfe631b92522b4957","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"2fb621cc_7552f923","updated":"2022-02-17 10:37:38.000000000","message":"TLDR: I\u0027m actually concerned that having two number-based versioning schemes in parallel would confuse people more than it helps them.\n\nOpenStack actually started with what this proposal proposes, (using numbers for official release names, and codenames for fun/marketing/dev purposes). Then as we added more components we allowed them to use different version numbers, while the \"integrated release\" was just using the name. So you would release \"Nova 24.0.0 and Swift 2.28.0 as part of OpenStack Xena\", have Neutron 19.0.0 in the stable/xena branch, and emit release announcements like \"oslo.policy 3.8.3 (xena)\".\n\nWith this proposal, you get more complex statements like \"Nova 25.0.0 and Swift 2.29.0 as part of OpenStack 2022.1\", stable branches that are called stable/2022.1 for versions like Neutron 20.0.0, or my personal favorite, release announcements that say \"oslo.db 11.2.0 (2022.1)\".\n\nI understand that it\u0027s sometimes difficult to map a named release to its original release date, but it seems like an easier challenge than explaining why you have stable branches called stable/2022.1 tracking a neutron release numbered 20.0.0.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"b2b456bc84bdae6bb560d22cdc2a3433f941404b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"b3c93bb6_f544ecc7","updated":"2022-02-17 14:18:43.000000000","message":"To be fair, this was the initial approach (\u003cyear\u003e.\u003crelease_count_within_the_year\u003e) to identify project versions/releases until Kilo. With Liberty we started to express how “old” was each individual project. I don’t remember the motivation, but considering the time period, it was probably related to the “big tent” and maturity “tags”.\n\nI understand Thierry\u0027s concerns, but in my view this proposal helps to clarify and map a release to a point in time. Something that we lost in Kilo - 2015 (yes, I needed to go check when Kilo was released).\n\nI think this is even more important now that we will start again with the alphabet (for the release name) and we are discussing a different release support cadence.\n\nIn terms of individual project versions I don’t think they need to be changed. In this case “Nova 27.0.0 is part of OpenStack release 2023.1” code named “Aardvark”.\n","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6418bf0d5ef5016b0372e691379779e5d1608630","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"582a1fec_0fb0bb7a","updated":"2022-02-16 16:37:16.000000000","message":"proposal lgtm, 1 comment on open voting to all community members","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"dc1df1f4d509a889028d009c5b031ff6d795cdde","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"dceb59c6_969737c2","in_reply_to":"28f6a55b_8a19a1fd","updated":"2022-02-17 14:52:07.000000000","message":"On the stable branch, are we going to do it with the version number or name? stable/2022.1 or stable/Axxx ? I think we need to clarify that too.\n\nI know it will create some confusion but at the same time it will clear out the timelines and how old my OpenStack version is (without going to check the release date of old releases). \n\nI agree on individual component versions are already confusing with the OpenStack main release and i do not think changing the OpenStack main release with a name or number or both add any more confusion.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"eaa9197057806dac483e529686d047eb2da25e78","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"28f6a55b_8a19a1fd","in_reply_to":"2fb621cc_7552f923","updated":"2022-02-17 11:28:39.000000000","message":"From my point of view, this is touching another subject which is versioning of different components. From my perspective as a deployer and knowing other deployers, I can say that the fact that different components have different version numbers is confusing already so it\u0027s not really made worse for practical purposes.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"666d918e6ebc5f14891bce5e001ec5cff6f48efb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"703e7d4c_b2b453fc","updated":"2022-02-22 15:02:09.000000000","message":"Looks good other than then rendering of the examples!","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"e087cc02e9b550bd84876a245d099ee99acd1bd0","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"af0905f8_d5118157","updated":"2022-02-22 14:54:55.000000000","message":"The updates look good.  Thanks!","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"04cb8ffde5ceb9a78edee6347a33450880d4fc17","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"f936dc11_9daae002","updated":"2022-02-22 20:47:51.000000000","message":"This could be a good way to differentiate between the first alphabet series and the second time around, which will be useful for things like the release automation. So +1 to the idea.","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"6c6dd7ba63536825665e6fbbda6685c59975c1b6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"477ad461_575aa75e","updated":"2022-03-10 15:40:05.000000000","message":"I am good with the latest iteration here.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"bbbad3340bcb2df9ec759bc6675a8ca0e4a545da","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"87a0913b_713078a3","updated":"2022-02-25 14:05:56.000000000","message":"Question inline.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":11292,"name":"Arne Wiebalck","email":"Arne.Wiebalck@cern.ch","username":"wiebalck"},"change_message_id":"be71a5c52eb177f9b827ca09e19654f169b584cb","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"7f2ec199_fc7022c1","updated":"2022-02-24 15:12:26.000000000","message":"Thanks, Belmiro!\n\nTwo questions/comments:\n\n- Will having a \u0027.\u0027 in the name create issues down the line, e.g. when it comes to URLs (such as per release repos)?\n\n- Would it make sense to take \u0027upgradability\u0027 somehow into account in the name given the proposed\n  tick/tock scheme (I know tick/tock is not approved yet)? With .1 and .2, and assuming .1 is the tick release the rules would be sth like:\n\n  yearN.1 (tick) -\u003e yearN.2 (tock), yearN+1.1 (tick)\n  yearN.2 (tock) -\u003e yearN+1.1 (tick)\n  \n  which is certainly better than what we would end up with the previous naming scheme, but I was wondering if that could be made more explicit. (I do not have a good suggestion for this, though.)\n  \n \n\n\n\n","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"6720e7a84c8faca9dd3367885cc478b47aa20e97","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"6e6b0017_aa8bd253","updated":"2022-03-09 16:43:04.000000000","message":"This gives us an unambiguous way to refer to each release; makes sense to me.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"9ca9d4cdc1084f31dbd6260d8ad2ab4c1999567b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"8640f8c7_f10876ed","updated":"2022-03-11 17:54:43.000000000","message":"let\u0027s merge it. no objection on it and let\u0027s start the numbering from next cycle. \n\nThanks Belmiro for working and proposing it.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b215688bddaf3dc4b15672e3b3af5584dcd9e7d5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"cb65bde6_3e910c5d","updated":"2022-03-09 01:08:36.000000000","message":"this looks in good shape for me.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"45f1bf2d1f608e04607d3d9dcf869bb9fb8fae21","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"92cbfa87_8a6d9ff3","in_reply_to":"7f2ec199_fc7022c1","updated":"2022-02-24 16:59:06.000000000","message":"Thanks Arne.\n- Not sure what you mean by release repos, but individual projects use tags for releases. Those won\u0027t change. Release notes URLs can continue to use the release name or just mask the \u0027.\u0027.\nI don\u0027t have a strong opinion here, though.\n\n- Do we really need to reflect the \u0027upgradability\u0027 into the release name? Operators will know that can skip \"tock\" releases and if we keep the current proposal yearN.1 will be always a \"tick\".\nI understand your suggestion, but I also don\u0027t have a better approach for it.\n\nI will let others to comment.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":11292,"name":"Arne Wiebalck","email":"Arne.Wiebalck@cern.ch","username":"wiebalck"},"change_message_id":"ddee289684fe7e648825b015c87a75807900f639","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":6,"id":"ef8c0ecc_f9472139","in_reply_to":"92cbfa87_8a6d9ff3","updated":"2022-02-24 18:00:07.000000000","message":"I was referring to the package (not git) repositories which carry the release name at the moment, e.g. https://trunk.rdoproject.org/centos8-xena. (A quick search seems to indicate it is technically possible to have dots in the URL path, but it is not clear if this is a good idea.)","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"}],"reference/release-naming.rst":[{"author":{"_account_id":30491,"name":"Radosław Piliszek","display_name":"Radek","email":"radek@piliszek.it","username":"yoctozepto","status":"self-employed techologist, collaborating mostly with 7bulls.com"},"change_message_id":"6cd9b96dfaee3f3f3ed524f7659d07d9a55ef933","unresolved":true,"context_lines":[{"line_number":5,"context_line":"Release Identification"},{"line_number":6,"context_line":"----------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Since the release \"Zed\", each OpenStack release has an "},{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example: \"2022.2\" where \"2022\" is the year of the release"}],"source_content_type":"text/x-rst","patch_set":2,"id":"8df2f6c1_d73453f2","line":8,"range":{"start_line":8,"start_character":0,"end_line":8,"end_character":6},"updated":"2022-02-16 16:04:17.000000000","message":"I\u0027m guessing \"After\"","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"fb7e17eba3a6b42013c4c8c21c6f3f8e5bca56fb","unresolved":true,"context_lines":[{"line_number":5,"context_line":"Release Identification"},{"line_number":6,"context_line":"----------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Since the release \"Zed\", each OpenStack release has an "},{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example: \"2022.2\" where \"2022\" is the year of the release"}],"source_content_type":"text/x-rst","patch_set":2,"id":"813bc390_703deba8","line":8,"range":{"start_line":8,"start_character":0,"end_line":8,"end_character":6},"in_reply_to":"7d51f452_c058dfb5","updated":"2022-02-17 14:23:43.000000000","message":"yes, it makes sense.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":15993,"name":"Amy Marrich","display_name":"Amy Marrich (spotz)","email":"amy@demarco.com","username":"amarrich"},"change_message_id":"2e1838b35ac40eeeb88a1384d88fd3963ff90958","unresolved":true,"context_lines":[{"line_number":5,"context_line":"Release Identification"},{"line_number":6,"context_line":"----------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Since the release \"Zed\", each OpenStack release has an "},{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example: \"2022.2\" where \"2022\" is the year of the release"}],"source_content_type":"text/x-rst","patch_set":2,"id":"0a3e5c32_f7062da9","line":8,"range":{"start_line":8,"start_character":0,"end_line":8,"end_character":6},"in_reply_to":"8df2f6c1_d73453f2","updated":"2022-03-28 14:28:11.000000000","message":"Following?","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6418bf0d5ef5016b0372e691379779e5d1608630","unresolved":true,"context_lines":[{"line_number":5,"context_line":"Release Identification"},{"line_number":6,"context_line":"----------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"Since the release \"Zed\", each OpenStack release has an "},{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example: \"2022.2\" where \"2022\" is the year of the release"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7d51f452_c058dfb5","line":8,"range":{"start_line":8,"start_character":0,"end_line":8,"end_character":6},"in_reply_to":"8df2f6c1_d73453f2","updated":"2022-02-16 16:37:16.000000000","message":"yeah.+1","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6418bf0d5ef5016b0372e691379779e5d1608630","unresolved":true,"context_lines":[{"line_number":11,"context_line":"Example: \"2022.2\" where \"2022\" is the year of the release"},{"line_number":12,"context_line":"and \"2\" represents the second release of the year. In this particular"},{"line_number":13,"context_line":"case, the second release of 2022."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"With this release identification schema we get an easy and sustainable"},{"line_number":16,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":17,"context_line":"ambiguity of the release name and alphabet iteration."}],"source_content_type":"text/x-rst","patch_set":2,"id":"256c34e9_27b62f6c","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":0},"updated":"2022-02-16 16:37:16.000000000","message":"so with this we will have something like below right?\n\nOpenStack 2023.1 Axxxx\nOpenStack 2023.2 Bxxxx\n\nIt will be good to add it as example for more clarity.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"fb7e17eba3a6b42013c4c8c21c6f3f8e5bca56fb","unresolved":true,"context_lines":[{"line_number":11,"context_line":"Example: \"2022.2\" where \"2022\" is the year of the release"},{"line_number":12,"context_line":"and \"2\" represents the second release of the year. In this particular"},{"line_number":13,"context_line":"case, the second release of 2022."},{"line_number":14,"context_line":""},{"line_number":15,"context_line":"With this release identification schema we get an easy and sustainable"},{"line_number":16,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":17,"context_line":"ambiguity of the release name and alphabet iteration."}],"source_content_type":"text/x-rst","patch_set":2,"id":"3c9e43c5_3107e832","line":14,"range":{"start_line":14,"start_character":0,"end_line":14,"end_character":0},"in_reply_to":"256c34e9_27b62f6c","updated":"2022-02-17 14:23:43.000000000","message":"+1","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6418bf0d5ef5016b0372e691379779e5d1608630","unresolved":true,"context_lines":[{"line_number":40,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":41,"context_line":"   OpenStack wiki."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":44,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":45,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":48,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"}],"source_content_type":"text/x-rst","patch_set":2,"id":"af0e5f82_72103b54","line":45,"range":{"start_line":43,"start_character":51,"end_line":45,"end_character":65},"updated":"2022-02-16 16:37:16.000000000","message":"I think we want to change this too to make all community members as electorate. something like:\n\n A Condorcet election is held to rank the names. The poll will be\n public, with the voting URL communicated through OpenStack mailing-lists\n (openstack-discuss and openstack-foundation).\n The poll will include the names along with any links to proposed names.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"ca6d5777f7a0b194beb1e81e809bcb22a7057e34","unresolved":true,"context_lines":[{"line_number":40,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":41,"context_line":"   OpenStack wiki."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":44,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":45,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":48,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"}],"source_content_type":"text/x-rst","patch_set":2,"id":"cbf7e956_2e095ac4","line":45,"range":{"start_line":43,"start_character":51,"end_line":45,"end_character":65},"in_reply_to":"6766c76c_decbacc9","updated":"2022-02-17 17:22:00.000000000","message":"Agree that this wording should be updated.  Fine with leaving it for a separate patch.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"dc1df1f4d509a889028d009c5b031ff6d795cdde","unresolved":true,"context_lines":[{"line_number":40,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":41,"context_line":"   OpenStack wiki."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":44,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":45,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":48,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"}],"source_content_type":"text/x-rst","patch_set":2,"id":"6766c76c_decbacc9","line":45,"range":{"start_line":43,"start_character":51,"end_line":45,"end_character":65},"in_reply_to":"7ff101ef_b59e8fdb","updated":"2022-02-17 14:52:07.000000000","message":"ok, sure. I am fine as a separate proposal.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"fb7e17eba3a6b42013c4c8c21c6f3f8e5bca56fb","unresolved":true,"context_lines":[{"line_number":40,"context_line":"   Criteria`_.  Proposed names should be added to a page on the"},{"line_number":41,"context_line":"   OpenStack wiki."},{"line_number":42,"context_line":""},{"line_number":43,"context_line":"#. A Condorcet election is held to rank the names. The electorate will be"},{"line_number":44,"context_line":"   Technical Committee, and the poll should  be run in a manner that allows"},{"line_number":45,"context_line":"   members of the community to see what each TC member voted for."},{"line_number":46,"context_line":""},{"line_number":47,"context_line":"#. The Foundation will perform a trademark check on the winning name."},{"line_number":48,"context_line":"   If there is a trademark conflict, then the Foundation will proceed"}],"source_content_type":"text/x-rst","patch_set":2,"id":"7ff101ef_b59e8fdb","line":45,"range":{"start_line":43,"start_character":51,"end_line":45,"end_character":65},"in_reply_to":"af0e5f82_72103b54","updated":"2022-02-17 14:23:43.000000000","message":"I was leaving this to a different proposal. I think we were still discussing who should be allowed to vote.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"303136729e247e47fc7c72d12695c0240231eed4","unresolved":true,"context_lines":[{"line_number":61,"context_line":"#. Each release name must start with the letter of the ISO basic Latin"},{"line_number":62,"context_line":"   alphabet following the initial letter of the previous release,"},{"line_number":63,"context_line":"   starting with the initial release of \"Austin\".  After \"Z\", the next"},{"line_number":64,"context_line":"   name should start with \"A\" again."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"#. The name must be composed only of the 26 characters of the ISO"},{"line_number":67,"context_line":"   basic Latin alphabet.  Names which can be transliterated into this"}],"source_content_type":"text/x-rst","patch_set":2,"id":"c6507b97_0e67e3fb","line":64,"range":{"start_line":64,"start_character":35,"end_line":64,"end_character":36},"updated":"2022-02-16 17:04:33.000000000","message":"we can add a line here about not to repeat the name which we already had for that letter in previous iteration.","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":7198,"name":"Jay Bryant","email":"jungleboyj@electronicjungle.net","username":"jsbryant"},"change_message_id":"ca6d5777f7a0b194beb1e81e809bcb22a7057e34","unresolved":true,"context_lines":[{"line_number":61,"context_line":"#. Each release name must start with the letter of the ISO basic Latin"},{"line_number":62,"context_line":"   alphabet following the initial letter of the previous release,"},{"line_number":63,"context_line":"   starting with the initial release of \"Austin\".  After \"Z\", the next"},{"line_number":64,"context_line":"   name should start with \"A\" again."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"#. The name must be composed only of the 26 characters of the ISO"},{"line_number":67,"context_line":"   basic Latin alphabet.  Names which can be transliterated into this"}],"source_content_type":"text/x-rst","patch_set":2,"id":"4da3c5e8_0b3c600d","line":64,"range":{"start_line":64,"start_character":35,"end_line":64,"end_character":36},"in_reply_to":"737d2cae_5831e078","updated":"2022-02-17 17:22:00.000000000","message":"+1","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"fb7e17eba3a6b42013c4c8c21c6f3f8e5bca56fb","unresolved":true,"context_lines":[{"line_number":61,"context_line":"#. Each release name must start with the letter of the ISO basic Latin"},{"line_number":62,"context_line":"   alphabet following the initial letter of the previous release,"},{"line_number":63,"context_line":"   starting with the initial release of \"Austin\".  After \"Z\", the next"},{"line_number":64,"context_line":"   name should start with \"A\" again."},{"line_number":65,"context_line":""},{"line_number":66,"context_line":"#. The name must be composed only of the 26 characters of the ISO"},{"line_number":67,"context_line":"   basic Latin alphabet.  Names which can be transliterated into this"}],"source_content_type":"text/x-rst","patch_set":2,"id":"737d2cae_5831e078","line":64,"range":{"start_line":64,"start_character":35,"end_line":64,"end_character":36},"in_reply_to":"c6507b97_0e67e3fb","updated":"2022-02-17 14:23:43.000000000","message":"+1","commit_id":"194ea821b93ba13e622eaec9775372117ce1d4c4"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"666d918e6ebc5f14891bce5e001ec5cff6f48efb","unresolved":true,"context_lines":[{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example:"},{"line_number":12,"context_line":"- OpenStack 2023.1 Axxxx"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Where \"2023\" is the year of the release, \"1\" represents the first release"},{"line_number":15,"context_line":"of the year and \"Axxxx\" is the release name following the release name rules."}],"source_content_type":"text/x-rst","patch_set":5,"id":"f62d6bf3_6a1e766a","line":12,"updated":"2022-02-22 15:02:09.000000000","message":"This doesn\u0027t render as a list, which I think was your intent.","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"28ad16e8e7c768d8d48ee76b3876197f0ba036b0","unresolved":false,"context_lines":[{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example:"},{"line_number":12,"context_line":"- OpenStack 2023.1 Axxxx"},{"line_number":13,"context_line":""},{"line_number":14,"context_line":"Where \"2023\" is the year of the release, \"1\" represents the first release"},{"line_number":15,"context_line":"of the year and \"Axxxx\" is the release name following the release name rules."}],"source_content_type":"text/x-rst","patch_set":5,"id":"f19dea36_a8ce8596","line":12,"in_reply_to":"f62d6bf3_6a1e766a","updated":"2022-02-24 13:18:55.000000000","message":"Ack","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":4393,"name":"Dan Smith","email":"dms@danplanet.com","username":"danms"},"change_message_id":"666d918e6ebc5f14891bce5e001ec5cff6f48efb","unresolved":true,"context_lines":[{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Other examples:"},{"line_number":18,"context_line":"- OpenStack 2023.2 Bxxxx"},{"line_number":19,"context_line":"- OpenStack 2024.1 Cxxxx"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"With this release identification schema we get an easy and sustainable"},{"line_number":22,"context_line":"approach to identify different OpenStack releases without dealing with the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"3ffb64e1_5ba5a117","line":19,"updated":"2022-02-22 15:02:09.000000000","message":"Nor does this. I think you at least need a blank line after the \"other examples:\"\n\nhttps://e10943dafba7c6eb888b-7e86d39a7e52fd605616e5700386a2b9.ssl.cf1.rackcdn.com/829563/5/check/openstack-tox-docs/f7513c8/docs/reference/release-naming.html","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"28ad16e8e7c768d8d48ee76b3876197f0ba036b0","unresolved":false,"context_lines":[{"line_number":16,"context_line":""},{"line_number":17,"context_line":"Other examples:"},{"line_number":18,"context_line":"- OpenStack 2023.2 Bxxxx"},{"line_number":19,"context_line":"- OpenStack 2024.1 Cxxxx"},{"line_number":20,"context_line":""},{"line_number":21,"context_line":"With this release identification schema we get an easy and sustainable"},{"line_number":22,"context_line":"approach to identify different OpenStack releases without dealing with the"}],"source_content_type":"text/x-rst","patch_set":5,"id":"7ca0690b_1e4dd30e","line":19,"in_reply_to":"3ffb64e1_5ba5a117","updated":"2022-02-24 13:18:55.000000000","message":"Ack","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":11904,"name":"Sean McGinnis","email":"sean.mcginnis@gmail.com","username":"SeanM"},"change_message_id":"04cb8ffde5ceb9a78edee6347a33450880d4fc17","unresolved":true,"context_lines":[{"line_number":22,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":23,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"The release identification schema doesn\u0027t replace the release name."},{"line_number":26,"context_line":"It\u0027s just an unambiguous way to identify OpenStack releases."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Release Name"}],"source_content_type":"text/x-rst","patch_set":5,"id":"4ee858e4_6b8f66a4","line":25,"updated":"2022-02-22 20:47:51.000000000","message":"It may be good to move this towards the top, before the first example. Currently, it states that a release will be year.number, but then gives examples with alphabetical values after it. I think it would be more clear to state that the proposal is to add the year.number value as an additional designation along with the current method of choosing an alphabetical name.\n\nThough with that said, I think it would be easier to just get rid of the naming and voting process and all that extra overhead all together and move to just having releases with the year.number designations.","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"28ad16e8e7c768d8d48ee76b3876197f0ba036b0","unresolved":true,"context_lines":[{"line_number":22,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":23,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"The release identification schema doesn\u0027t replace the release name."},{"line_number":26,"context_line":"It\u0027s just an unambiguous way to identify OpenStack releases."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Release Name"}],"source_content_type":"text/x-rst","patch_set":5,"id":"c007b380_4ae90737","line":25,"in_reply_to":"4ee858e4_6b8f66a4","updated":"2022-02-24 13:18:55.000000000","message":"yeah... That was the initial idea but I feel that we will find a lot of resistance if we drop the name. To be honest, year.number is nothing new. We used this schema until 2015 and then dropped it to only the release name.","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"89af6e3ef2d695e651b99c3fac1df30c30ddbb0a","unresolved":true,"context_lines":[{"line_number":22,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":23,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"The release identification schema doesn\u0027t replace the release name."},{"line_number":26,"context_line":"It\u0027s just an unambiguous way to identify OpenStack releases."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Release Name"}],"source_content_type":"text/x-rst","patch_set":5,"id":"42f84b99_36080f6d","line":25,"in_reply_to":"a842cd8f_e9fec21c","updated":"2022-03-09 14:29:01.000000000","message":"we will discuss it more in PTG and see if we can remove or make it better (less controversial :)). \n\nBut let\u0027s do this first which is adding the number versioning in the release and allowing us to think about dropping names.","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":11975,"name":"Slawek Kaplonski","email":"skaplons@redhat.com","username":"slaweq"},"change_message_id":"e10c35a520150f88ade18eacfee8eab0df58e384","unresolved":true,"context_lines":[{"line_number":22,"context_line":"approach to identify different OpenStack releases without dealing with the"},{"line_number":23,"context_line":"ambiguity of the release name and alphabet iteration."},{"line_number":24,"context_line":""},{"line_number":25,"context_line":"The release identification schema doesn\u0027t replace the release name."},{"line_number":26,"context_line":"It\u0027s just an unambiguous way to identify OpenStack releases."},{"line_number":27,"context_line":""},{"line_number":28,"context_line":"Release Name"}],"source_content_type":"text/x-rst","patch_set":5,"id":"a842cd8f_e9fec21c","line":25,"in_reply_to":"c007b380_4ae90737","updated":"2022-03-09 07:33:03.000000000","message":"Giving last discussion in the tc channel about \"Zed\" name, we may still want to go back to the year.number only [1].\nBut personally I think that having some \"marketing name\" too is good and we should keep it like that.\n\n[1] https://meetings.opendev.org/irclogs/%23openstack-tc/%23openstack-tc.2022-03-08.log.html#t2022-03-08T14:35:26","commit_id":"3e06ba3b907d4b0f4665016c27e0bb71a8e87e7d"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"bbbad3340bcb2df9ec759bc6675a8ca0e4a545da","unresolved":true,"context_lines":[{"line_number":5,"context_line":"Release Identification"},{"line_number":6,"context_line":"----------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"After the release \"Zed\", each OpenStack release has an"},{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example:"}],"source_content_type":"text/x-rst","patch_set":6,"id":"79df3cf3_2ad63248","line":8,"range":{"start_line":8,"start_character":0,"end_line":8,"end_character":23},"updated":"2022-02-25 14:05:56.000000000","message":"I don\u0027t think we have to say \"after Zed\" here, because if I understand this correctly, you\u0027re not proposing this as an actual versioning designator as it was in the past (the Kilo release of cinder was version 2015.1.0 tagged on 2015-04-30, whereas the Xena release of cinder was version 19.0.0 tagged on 2021-10-06).  So we could just agree that the way we want to refer to releases in official communication follows the scheme you outline here.  Thus, we can start referring to historical releases as:\n\n  OpenStack 2021.2 \"Xena\"\n  ...\n  OpenStack 2012.1 \"Essex\"\n  OpenStack 2011.3 \"Diablo\"\n  OpenStack 2011.2 \"Cactus\"\n  OpenStack 2011.1 \"Bexar\"\n  OpenStack 2010.1 \"Austin\"\n\nand the OpenStack 2022.1 \"Yoga\" release will contain cinder 20.0.0.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"b215688bddaf3dc4b15672e3b3af5584dcd9e7d5","unresolved":true,"context_lines":[{"line_number":5,"context_line":"Release Identification"},{"line_number":6,"context_line":"----------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"After the release \"Zed\", each OpenStack release has an"},{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example:"}],"source_content_type":"text/x-rst","patch_set":6,"id":"d43b443d_9145422f","line":8,"range":{"start_line":8,"start_character":0,"end_line":8,"end_character":23},"in_reply_to":"249bcbff_b3d468a3","updated":"2022-03-09 01:08:36.000000000","message":"I agree with Belmiro here. and I do not think we should reflect this for past releases. Project versioning is completely different and we are not touching those in this proposal.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"},{"author":{"_account_id":2033,"name":"Belmiro Moreira","email":"moreira.belmiro.email.lists@gmail.com","username":"moreira-belmiro-email-lists"},"change_message_id":"4a166e5b615f39880d51776e800cc2d0befc2333","unresolved":true,"context_lines":[{"line_number":5,"context_line":"Release Identification"},{"line_number":6,"context_line":"----------------------"},{"line_number":7,"context_line":""},{"line_number":8,"context_line":"After the release \"Zed\", each OpenStack release has an"},{"line_number":9,"context_line":"identification code: \"year\".\"release count within the year\""},{"line_number":10,"context_line":""},{"line_number":11,"context_line":"Example:"}],"source_content_type":"text/x-rst","patch_set":6,"id":"249bcbff_b3d468a3","line":8,"range":{"start_line":8,"start_character":0,"end_line":8,"end_character":23},"in_reply_to":"79df3cf3_2ad63248","updated":"2022-02-28 16:14:35.000000000","message":"The proposal is to change the release identification/name, not project versions. Until now, releases only have a name (\"Austin\", \"Bexar\", ...). The proposal is that starting with the \"restart\" of the alphabet (after Zed) we can start referring to releases also with \"yearN.X\". Example: OpenStack 2023.1 Axxxx\n\nNot sure if we can/should reflect this in past releases.\nWhen we changed the project versioning, we continue to refer to earlier projects versions using the \"old\" schema (For example: 2015.1).\n\nAfter Zed, we will have the release \"2023.1 Axxxx\" with the Cinder version 22.0.0  \n\nLet me know if it makes sense.","commit_id":"aaa531c75d76d6996dccd6dc373e603ab9a5057a"}]}