)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"mangust404@gmail.com","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"3eb766aa07977370358997214008965cf8d6643b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"c3704d8e_11e96526","updated":"2026-07-16 16:03:51.000000000","message":"LGTM","commit_id":"2622475cc1730e196664fbe2b58d978ee25e62e7"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"9c68464b2f9ce900567732059e15ee3ced6b280e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"084f932e_339be709","updated":"2026-07-20 12:14:47.000000000","message":"by checking the test job logs I see, that there are some changes (see upgrade notes [1] for example) that would warrant a MINOR version bump. (also note, that stable policy does not allow backporting patches that would change default values of configuration changes - as this could cause issues when an operator upgrades an existing deployment -, however trove is not listed among projects that follow stable policy [2]. still, this is better to follow if possible, to make operators life easier). Let me update the version of the new release (we have room for it, as 23.1.0 is not used on newer branches, given trove has cycle-with-rc release model).\n\n[1] https://zuul.opendev.org/t/openstack/build/ab64e482f96145db8a2a23ca17f41c62/log/tox/list-changes/list-changes-results.log#936\n[2] https://docs.openstack.org/project-team-guide/stable-branches.html#project-teams-which-asserted-they-follow-the-stable-branch-policy","commit_id":"2622475cc1730e196664fbe2b58d978ee25e62e7"},{"author":{"_account_id":36080,"name":"Erkin Mussurmankulov","display_name":"Eric","email":"mangust404@gmail.com","username":"mongoose404","status":"PS Cloud services employee"},"change_message_id":"615adf4549d36a158129531c579b5b0caf0973aa","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"239d71a6_bd045780","in_reply_to":"084f932e_339be709","updated":"2026-07-20 16:13:41.000000000","message":"Thank you for the clarification and explanations. I\u0027m still learning, as it\u0027s my first release cycle as a PTL, and I don\u0027t see what else I can do except just set CR+1 🙂","commit_id":"2622475cc1730e196664fbe2b58d978ee25e62e7"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"3df078c802a76344c4036a537fa6c4023a7ef35b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"4bdf9604_6d2bab53","in_reply_to":"239d71a6_bd045780","updated":"2026-07-21 08:02:31.000000000","message":"Hi Eric, no problem :) what usually you can do is something like this:\n* check that all the necessary patches are merged and included in the given branch (check for open patches)\n* check that the hash is correct\n* check that the version bump is correct (we mostly follow Semantic Versioning [1], with some exceptions)\n\nand we are exactly looking for a Code-Review+1 from PTL or the team\u0027s release liaison, so that we know that the team thinks that the release is ready to ship. :) \nfeel free to ping me/us if you have any question either here on release patches or on #openstack-release IRC channel.\n\nbtw, you can push release patches yourself, if it is needed by the project. there is a new-release command [2] in releases repository for this (so that you avoid copy-paste errors ;))\n\n[1] https://semver.org\n[2] https://releases.openstack.org/reference/using.html#using-new-release-command","commit_id":"2622475cc1730e196664fbe2b58d978ee25e62e7"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"6abe26e8f9da59f4906074f21956b77afe032cb2","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8d6acc2d_0ebb65e8","updated":"2026-07-21 08:04:24.000000000","message":"LGTM:\n* MINOR version bump ✅ (see comments above)\n* PTL-Approved+1 label exists ✅\n* no issues found in test job logs","commit_id":"95d668137e03e51d537f440529427a62a855c72a"}]}