)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"fb275bce4c0cdb870ca42f26d37f8cde820bf906","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"0efc07fc_90906e07","updated":"2024-02-23 09:34:31.000000000","message":"Hi Jens, I\u0027ve a reply inline with my understanding of why we do it this way","commit_id":"c37bb9f79ddf8a3878de967b09119f349a0a0d48"},{"author":{"_account_id":5314,"name":"Brian Rosmaita","email":"rosmaita.fossdev@gmail.com","username":"brian-rosmaita"},"change_message_id":"5d8eec3fab4e9b9738dfeade7526553fb16a772b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"b6153cfd_cd332222","updated":"2024-02-14 21:02:53.000000000","message":"Verified the hash.  Minor increment on version number seems correct due to all the NVMe-oF fixes.","commit_id":"c37bb9f79ddf8a3878de967b09119f349a0a0d48"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"47913010daf8cc6d67f5457f189bb600e930b301","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"a0ea048a_08a94c1b","updated":"2024-02-23 09:19:25.000000000","message":"does this need to depend on the 2023.2 releases? currently this release is blocked because it is stacked on top of the 2023.2 patch","commit_id":"c37bb9f79ddf8a3878de967b09119f349a0a0d48"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"db9545b64877c1b42b3cca2d2056e66b2a75bd46","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"2f50d781_7e830de3","updated":"2024-02-22 17:00:32.000000000","message":"hash and version bump LGTM","commit_id":"c37bb9f79ddf8a3878de967b09119f349a0a0d48"},{"author":{"_account_id":27615,"name":"Rajat Dhasmana","email":"rajatdhasmana@gmail.com","username":"whoami-rajat"},"change_message_id":"fb275bce4c0cdb870ca42f26d37f8cde820bf906","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"1c8a7350_99d45869","in_reply_to":"a0ea048a_08a94c1b","updated":"2024-02-23 09:34:31.000000000","message":"according to the stable branch release policy, releases should happen in recent branch first manner[1]. IMO Its to avoid issues with upgrades if we release antelope and forget releasing bobcat then after upgrade, we might not have fixes in bobcat that were in antelope.\n\nAlso the 2023.2 patch looks ready and can be merged.\n\n[1] https://docs.openstack.org/project-team-guide/stable-branches.html#releases","commit_id":"c37bb9f79ddf8a3878de967b09119f349a0a0d48"},{"author":{"_account_id":13252,"name":"Dr. Jens Harbott","display_name":"Jens Harbott (frickler)","email":"frickler@offenerstapel.de","username":"jrosenboom"},"change_message_id":"25ee5bf712a28555fd334fa4603a665e366b552a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"43c0e14b_1254b1bd","updated":"2024-02-23 10:20:23.000000000","message":"ok, that makes sense, I didn\u0027t check whether there were the same fixes in both releases\n\nin this case this patch was lacking a rebase in order to be mergable which I have now done. will approve again once the 2023.2 patch is approved","commit_id":"1fc79f70334d249f57eec0d24e50ff6dc57ef8c1"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"6ca9aefcd8db16b4cf85548921f65a19f94cd3fd","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"eb80a14d_e4660e06","updated":"2024-02-23 13:23:27.000000000","message":"parent has merged, we can release this, too","commit_id":"1fc79f70334d249f57eec0d24e50ff6dc57ef8c1"}]}