)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"4c21cc1af0a2c631db42a14cc55808d75a0a6321","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"3be3c8c4_bc33ecb0","updated":"2025-01-09 13:46:44.000000000","message":"well, we have \u0027python_requires \u003d \u003e\u003d3.9\u0027 added, so similarly like with the other 2023.1-last tags i\u0027d use here a version which still has py38 support for the sake of 2023.1 Antelope\u0027s supported runtime consistency. So either use hash `489408a1f5d5b07d10ffda245aaeae031de588df` or use the existing 2.9.0 release?","commit_id":"68a21e677cf7c3e90d0db5beba3482277150c35a"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"6512cbbcc27c236aae5ff18e0286afd351478d78","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"8f27a80e_366423d7","in_reply_to":"3be3c8c4_bc33ecb0","updated":"2025-01-10 22:29:43.000000000","message":"done","commit_id":"68a21e677cf7c3e90d0db5beba3482277150c35a"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"fbef9eac951108306b3ea86e276e49949705df7c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":4,"id":"7b0828fd_d1fb8f54","in_reply_to":"8f27a80e_366423d7","updated":"2025-01-13 15:49:04.000000000","message":"Sorry I suggested a wrong hash as this is not the parent of the problematic py38 dropping patch :S Let me fix this quickly.","commit_id":"68a21e677cf7c3e90d0db5beba3482277150c35a"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"d0ebb4988ed6e3f8ef20d738d47ebeacb3dca7d3","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":5,"id":"fd7a8b5d_e15f4cae","updated":"2025-01-13 15:21:41.000000000","message":"thanks for confirming","commit_id":"cde78faa4b9a3c05754279bb113a0b80ca08e018"}],"deliverables/epoxy/neutron-tempest-plugin.yaml":[{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"22805143d960e00be35857d78086dd82a62130f8","unresolved":true,"context_lines":[{"line_number":13,"context_line":"  - version: 2.10.0"},{"line_number":14,"context_line":"    projects:"},{"line_number":15,"context_line":"      - repo: openstack/neutron-tempest-plugin"},{"line_number":16,"context_line":"        hash: 489408a1f5d5b07d10ffda245aaeae031de588df"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"a9f920d4_d9004cae","line":16,"updated":"2025-01-12 18:32:28.000000000","message":"Ok, so then the plan would be to create a new version/tag for E-next once this change merges, just since this hash is quite old?","commit_id":"cde78faa4b9a3c05754279bb113a0b80ca08e018"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"1c65f193eaa03716cbb76411f8822cc805c8eefc","unresolved":true,"context_lines":[{"line_number":13,"context_line":"  - version: 2.10.0"},{"line_number":14,"context_line":"    projects:"},{"line_number":15,"context_line":"      - repo: openstack/neutron-tempest-plugin"},{"line_number":16,"context_line":"        hash: 489408a1f5d5b07d10ffda245aaeae031de588df"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"cc60f95b_0e327c9f","line":16,"in_reply_to":"a9f920d4_d9004cae","updated":"2025-01-13 08:30:00.000000000","message":"yepp. this cut is really for just tagging the branch at the point where 2023.1 Antelope transitioned to unmaintained from stable, i.e. the point where (hopefully) tempest was fully functional for stable/2023.1.\n\n(In the past we didn\u0027t really use \\*-last tags as tempest from master worked most of the cases for old stable branches (in Extended Maintenance), but now that we started to drop py38 support in tempest it breaks unmaintained/* branches)\n\nAfter that, feel free to cut a release for neutron-tempest-plugin whenever you see fit.","commit_id":"cde78faa4b9a3c05754279bb113a0b80ca08e018"},{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"48ed631818b7747de502c8fd039676daeb44054e","unresolved":false,"context_lines":[{"line_number":13,"context_line":"  - version: 2.10.0"},{"line_number":14,"context_line":"    projects:"},{"line_number":15,"context_line":"      - repo: openstack/neutron-tempest-plugin"},{"line_number":16,"context_line":"        hash: 489408a1f5d5b07d10ffda245aaeae031de588df"}],"source_content_type":"text/x-yaml","patch_set":5,"id":"28e4b373_38654a25","line":16,"in_reply_to":"cc60f95b_0e327c9f","updated":"2025-01-13 19:48:00.000000000","message":"yeah,latest changes can be released after this. As Elod mentioned, this is just to tag 2023.1 last.","commit_id":"cde78faa4b9a3c05754279bb113a0b80ca08e018"}]}