)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":28522,"name":"Hervé Beraud","email":"herveberaud.pro@gmail.com","username":"hberaud"},"change_message_id":"caeeb0ee0cc5874017b0d22177cd2b7ad1945832","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"df4cb83d_d5411aa8","updated":"2023-08-31 13:25:33.000000000","message":"IMO the current version looks good. Let\u0027s wait Tim\u0027s feedback.","commit_id":"e96484f33dc432a5498861b69101bec5d32eb036"},{"author":{"_account_id":308,"name":"Thierry Carrez","email":"thierry@openstack.org","username":"ttx"},"change_message_id":"75c9b83ceb0ec90c2a7c780a202a427e27827936","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"5c333ca2_8b48a6a3","updated":"2023-08-31 09:42:02.000000000","message":"LGTM","commit_id":"e96484f33dc432a5498861b69101bec5d32eb036"}],"deliverables/bobcat/swift.yaml":[{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"69f4df54df6bd38799f85357ffd70fdee0ce5b5c","unresolved":true,"context_lines":[{"line_number":6,"context_line":"repository-settings:"},{"line_number":7,"context_line":"  openstack/swift: {}"},{"line_number":8,"context_line":"releases:"},{"line_number":9,"context_line":"  - version: 2.32.0"},{"line_number":10,"context_line":"    projects:"},{"line_number":11,"context_line":"      - repo: openstack/swift"},{"line_number":12,"context_line":"        hash: 191b627b856bc2e8eaa4049521e3476bf29ed40c"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"85257cd5_717af571","line":9,"updated":"2023-08-31 12:32:42.000000000","message":"reno suggests 3.0.0, based on the upgrade notes [1]. I\u0027m not sure we need th MAJOR bump. @Tim, could you please double check?\n\n[1] https://zuul.opendev.org/t/openstack/build/c7e6561418314a5aa5c92a4f6001f175/log/tox/list-changes/list-changes-results.log#3484-3505","commit_id":"e96484f33dc432a5498861b69101bec5d32eb036"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"8c22d77f079194e572eb4ec9ee36e57583541733","unresolved":false,"context_lines":[{"line_number":6,"context_line":"repository-settings:"},{"line_number":7,"context_line":"  openstack/swift: {}"},{"line_number":8,"context_line":"releases:"},{"line_number":9,"context_line":"  - version: 2.32.0"},{"line_number":10,"context_line":"    projects:"},{"line_number":11,"context_line":"      - repo: openstack/swift"},{"line_number":12,"context_line":"        hash: 191b627b856bc2e8eaa4049521e3476bf29ed40c"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"86c8274b_0b12e5ea","line":9,"in_reply_to":"459989ff_4f374942","updated":"2023-09-01 13:24:36.000000000","message":"Thanks for the detailed answer Tim, approving the patch based on it!","commit_id":"e96484f33dc432a5498861b69101bec5d32eb036"},{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"ef9d164246aa75fe57b61efc8b9840a6c08ad6ea","unresolved":true,"context_lines":[{"line_number":6,"context_line":"repository-settings:"},{"line_number":7,"context_line":"  openstack/swift: {}"},{"line_number":8,"context_line":"releases:"},{"line_number":9,"context_line":"  - version: 2.32.0"},{"line_number":10,"context_line":"    projects:"},{"line_number":11,"context_line":"      - repo: openstack/swift"},{"line_number":12,"context_line":"        hash: 191b627b856bc2e8eaa4049521e3476bf29ed40c"}],"source_content_type":"text/x-yaml","patch_set":1,"id":"459989ff_4f374942","line":9,"in_reply_to":"85257cd5_717af571","updated":"2023-08-31 15:36:12.000000000","message":"2.32.0 seems right to me.\n\n- I could see an argument that the config-parsing change is breaking, but the behavior was so varied before (some daemons would parse upper-cased config keys as though they were lower-cased, while others would just ignore them) that no sane operator would have been relying on it. I wanted to call it out with an upgrade note on the off-chance that it would jog someone\u0027s memory.\n\n- The cache-structure change is very much *not* breaking -- we intentionally have the old and new structures use different namespaces, so both old and new code will work at the same time. The upgrade note is to call out the potential for a thundering-herd problem, which is likely to be particularly acute with sharded containers. That said, the recommended staged-rollout is generally-accepted good practice; the expectation is that most operators would be doing this already, particularly at the scale at which the problem is most likely to arise.\n\n- The deprecation is just that: a deprecation. Nothing has been turned off; no support has been removed. If it turns out we still have users needing [netifaces](https://pypi.org/project/netifaces/), we may reverse that decision or (more likely, given [the state of the project](https://lists.openstack.org/pipermail/openstack-discuss/2023-April/033261.html)) find some other way to get the currently-bound IP addresses.\n\nFWIW, when we do eventually do a major version bump, it\u0027ll likely be to 4.0.0, just to avoid confusion with [swift3](https://opendev.org/x/swift3), the old S3-compatibility middleware.","commit_id":"e96484f33dc432a5498861b69101bec5d32eb036"}]}