)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"01fa406422f76408415e79e62cbad8869318c92c","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"247c413f_724ece45","updated":"2024-09-30 10:23:01.000000000","message":"-1 just for the question (to other reviewers)","commit_id":"7df5458e16920f2e3a1380f140e7a14ef194e123"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"55fd7ad56864bde2e4f8c0da59ac23ec1499e547","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"ee8c0d7e_bf9709f0","updated":"2024-10-03 12:54:29.000000000","message":"recheck bug 2083609","commit_id":"326fcbafd9bd0ef25bd289d9fa52a9a03d4a2b50"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"011a51d121a750424f849559f6526041772987e8","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"8fc27407_40e02716","updated":"2024-10-09 21:12:04.000000000","message":"recheck deprecation is not a functional change","commit_id":"326fcbafd9bd0ef25bd289d9fa52a9a03d4a2b50"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"88adbcef393791cb6a371b29a2d11cfc7df71fd6","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"906322fb_b23f0e66","updated":"2024-10-07 17:33:12.000000000","message":"recheck fullstack doesn\u0027t test ovn","commit_id":"326fcbafd9bd0ef25bd289d9fa52a9a03d4a2b50"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"5f62cbdd4f3841ab6816a9347fb08688a921049e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"053f4c00_9987e48e","updated":"2024-10-04 19:36:13.000000000","message":"recheck neutron-fullstack-with-uwsgi","commit_id":"326fcbafd9bd0ef25bd289d9fa52a9a03d4a2b50"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"c094ed735023fbed8c06dbab00153fa191d9eb7b","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"7ca0d523_e0782535","updated":"2024-10-07 10:32:18.000000000","message":"recheck neutron-functional-with-uwsgi","commit_id":"326fcbafd9bd0ef25bd289d9fa52a9a03d4a2b50"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"d7c27aaf1070575ba201167942c2ec7d32aa1425","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"904c0090_fc197e72","updated":"2024-10-04 06:31:34.000000000","message":"recheck neutron-tempest-plugin-ovn-enforce-scope-old-defaults","commit_id":"326fcbafd9bd0ef25bd289d9fa52a9a03d4a2b50"}],"releasenotes/notes/deprecate-ovn_emit_need_to_frag-f27859b234213d12.yaml":[{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"01fa406422f76408415e79e62cbad8869318c92c","unresolved":true,"context_lines":[{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``ovn_emit_need_to_frag`` option is now deprecated for removal. The"},{"line_number":5,"context_line":"    config option will removed in the ``2025.2`` release."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"7688d542_660e81cb","line":5,"range":{"start_line":5,"start_character":40,"end_line":5,"end_character":46},"updated":"2024-09-30 10:23:01.000000000","message":"If we deprecate a config option in a SLURP release, should we remove it in the next SLURP release (2026.1)?","commit_id":"7df5458e16920f2e3a1380f140e7a14ef194e123"},{"author":{"_account_id":1131,"name":"Brian Haley","email":"haleyb.dev@gmail.com","username":"brian-haley"},"change_message_id":"7e45a1125a1bbed8e49c01e554e291867f75d795","unresolved":true,"context_lines":[{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``ovn_emit_need_to_frag`` option is now deprecated for removal. The"},{"line_number":5,"context_line":"    config option will removed in the ``2025.2`` release."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"6d9497b0_d8f542c8","line":5,"range":{"start_line":5,"start_character":40,"end_line":5,"end_character":46},"in_reply_to":"0ee2c2ee_7131a144","updated":"2024-09-30 17:56:36.000000000","message":"I am also confused by the doc, but would think release+2 is better, so 2026.1.","commit_id":"7df5458e16920f2e3a1380f140e7a14ef194e123"},{"author":{"_account_id":16688,"name":"Rodolfo Alonso","email":"ralonsoh@redhat.com","username":"rodolfo-alonso-hernandez"},"change_message_id":"eb4e15cc341400b12b1656cbb5037a82bad8980b","unresolved":false,"context_lines":[{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``ovn_emit_need_to_frag`` option is now deprecated for removal. The"},{"line_number":5,"context_line":"    config option will removed in the ``2025.2`` release."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"dd3249c3_d3249b89","line":5,"range":{"start_line":5,"start_character":40,"end_line":5,"end_character":46},"in_reply_to":"42a888f8_f546649e","updated":"2024-10-02 06:59:35.000000000","message":"Yeah, I think I found it (from [1]):\n\"\"\"\nSince the deprecation, waiting, and removal can only happen in “SLURP” releases, the result is also that the minimum length of time that things may be deprecated before removal will increase as well.\n\"\"\"\n\nSo I think we should mark this for removal in 2026.1. In any case, because 2025.2 is a non SLURP release, if this config option is removed in the next release, the change will take effect in 2026.2.\n\nI\u0027ll +2 this patch but we usually give at least 2 releases to remove a deprecated config option.\n\n[1]https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html","commit_id":"7df5458e16920f2e3a1380f140e7a14ef194e123"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"17d270da9332baf638ed19e3d3aaa69c3a96ce9e","unresolved":true,"context_lines":[{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``ovn_emit_need_to_frag`` option is now deprecated for removal. The"},{"line_number":5,"context_line":"    config option will removed in the ``2025.2`` release."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"42a888f8_f546649e","line":5,"range":{"start_line":5,"start_character":40,"end_line":5,"end_character":46},"in_reply_to":"6d9497b0_d8f542c8","updated":"2024-09-30 20:48:02.000000000","message":"better as in safer?\n\nAFAIU if you deprecate in tick release (slurp), then you can remove in tock (slurp+1); but if you deprecate in tock (slurp-1), then you can\u0027t remove until next tock (slurp+1). This patch is to be merged in tick (slurp), so it\u0027s \"ok\" to remove in 2025.2. What\u0027s an argument to wait for slurp+1 cut-off to be able to delete it?\n\n(The option is for old kernels only; are we concerned about these?)","commit_id":"7df5458e16920f2e3a1380f140e7a14ef194e123"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"b0397b9feb9363c43b0d94757470d2ae707df6e0","unresolved":true,"context_lines":[{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``ovn_emit_need_to_frag`` option is now deprecated for removal. The"},{"line_number":5,"context_line":"    config option will removed in the ``2025.2`` release."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"0ee2c2ee_7131a144","line":5,"range":{"start_line":5,"start_character":40,"end_line":5,"end_character":46},"in_reply_to":"7688d542_660e81cb","updated":"2024-09-30 17:12:41.000000000","message":"Good question. https://docs.openstack.org/project-team-guide/deprecation.html is talking about 12 months but the examples it gives are a bit confusing (to me). The document talks about tick and tock releases. It also links to release cadence page: https://governance.openstack.org/tc/resolutions/20220210-release-cadence-adjustment.html but it doesn\u0027t explain which release is \"tick\" and which is \"tock\". (SLURP or non-SLURP?)\n\nDo you understand the terms (tick and tock) used by the document?","commit_id":"7df5458e16920f2e3a1380f140e7a14ef194e123"},{"author":{"_account_id":9656,"name":"Ihar Hrachyshka","email":"ihrachys@redhat.com","username":"ihrachys","status":"Red Hat Networking Systems Engineer"},"change_message_id":"93d1f63751cbdd08e92029445c4ef5200a8dac8c","unresolved":false,"context_lines":[{"line_number":2,"context_line":"deprecations:"},{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``ovn_emit_need_to_frag`` option is now deprecated for removal. The"},{"line_number":5,"context_line":"    config option will removed in the ``2025.2`` release."}],"source_content_type":"text/x-yaml","patch_set":1,"id":"0f175aa0_eaae3e92","line":5,"range":{"start_line":5,"start_character":40,"end_line":5,"end_character":46},"in_reply_to":"dd3249c3_d3249b89","updated":"2024-10-02 12:43:34.000000000","message":"I guess it\u0027s easier not to think about tick-tock and just always do two...","commit_id":"7df5458e16920f2e3a1380f140e7a14ef194e123"}]}