)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"4eb968b28aa9784f113c433271eff6a6cfd09cd7","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":7,"id":"2fe50487_9e901833","updated":"2026-10-14 07:09:58.000000000","message":"This shouldn\u0027t be done directly. We should add a warning log, first, in case quorum queues are not used without any behavior change. And keep the warning for a few cycles and the make the switch.","commit_id":"398cc1ef5fca94e8827e1686acf569559f6178f8"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@chainguard.dev","username":"toabctl"},"change_message_id":"0e188f22c4179e1fd0b030b26c485b5f14626c80","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":7,"id":"da6faa9a_1ef57276","in_reply_to":"2fe50487_9e901833","updated":"2026-10-14 07:33:18.000000000","message":"@kajinamit@oss.nttdata.com better now? or should I be more precise in which release we will enable it by default? maybe 2027.1 ?","commit_id":"398cc1ef5fca94e8827e1686acf569559f6178f8"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@chainguard.dev","username":"toabctl"},"change_message_id":"c171db3a3535f22637167bbdb00e3a68cf7fc864","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"e1ab70c6_281fc746","in_reply_to":"4cd535bf_ab871bdc","updated":"2026-10-14 07:44:36.000000000","message":"ok. so I\u0027ll keep the change as is.","commit_id":"398cc1ef5fca94e8827e1686acf569559f6178f8"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"d4c6549420b3a732d02624738af1442c0ea86e99","unresolved":true,"context_lines":[],"source_content_type":"","patch_set":7,"id":"4cd535bf_ab871bdc","in_reply_to":"da6faa9a_1ef57276","updated":"2026-10-14 07:42:10.000000000","message":"We shouldn\u0027t enable it in 2027.1. I expect the switch can happen in 2027.2 earliest, but we may decide later based on feedbacks. I suspect that people are not yet bothered by this due to a bit old rabbitmq packages available in their distro (mainly in ubuntu or debian).\n\nI\u0027d suggest we don\u0027t have to mention the target release now because I don\u0027t want to update this later when we get some feedbacks to delay it.","commit_id":"398cc1ef5fca94e8827e1686acf569559f6178f8"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@chainguard.dev","username":"toabctl"},"change_message_id":"fd5c0744bbc0817a0ae3298a4bceffd16c3eb2f5","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":8,"id":"e2b7344d_37c99198","updated":"2026-10-14 12:40:34.000000000","message":"@arnaud.morin@gmail.com could you have another look please?","commit_id":"840088432d0741e079ba244636bd93e38a28382a"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"55e679ccdf22fab804e641733c34d5d180fa2eed","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":8,"id":"1584b3a6_644da3bb","updated":"2026-10-14 07:43:56.000000000","message":"The direction looks good to me. I have to come back to this later to review the contents.","commit_id":"840088432d0741e079ba244636bd93e38a28382a"}],"releasenotes/notes/quorum-queues-by-default-3f1b2c7d9e8a4b56.yaml":[{"author":{"_account_id":11583,"name":"Arnaud Morin","email":"arnaud.morin@gmail.com","username":"arnaudmorin"},"change_message_id":"871c91c6c91ed93b2b154e39b13fa285623fb39f","unresolved":true,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``[oslo_messaging_rabbit] rabbit_quorum_queue`` and"},{"line_number":5,"context_line":"    ``[oslo_messaging_rabbit] rabbit_transient_quorum_queue`` options now"},{"line_number":6,"context_line":"    default to ``True``. RabbitMQ 4.3.0 refuses to create transient"},{"line_number":7,"context_line":"    (non-durable) non-exclusive queues by default (see the `RabbitMQ 4.3.0"},{"line_number":8,"context_line":"    release notes"},{"line_number":9,"context_line":"    \u003chttps://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0\u003e`__),"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"3a51cd35_a3b08e1c","line":6,"updated":"2026-10-13 08:13:52.000000000","message":"This is a hard/breaking change that needs to be very visible. Is there any way to make this bold/red or whatever in the release note? Also maybe worth notifying other projects (nova, neutron, etc.) about this?","commit_id":"595eb9df474380357a9cdb77dc3c8f466fad8cf2"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@chainguard.dev","username":"toabctl"},"change_message_id":"7e567d54bff24ae161a333f636704fef0e4e1513","unresolved":true,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``[oslo_messaging_rabbit] rabbit_quorum_queue`` and"},{"line_number":5,"context_line":"    ``[oslo_messaging_rabbit] rabbit_transient_quorum_queue`` options now"},{"line_number":6,"context_line":"    default to ``True``. RabbitMQ 4.3.0 refuses to create transient"},{"line_number":7,"context_line":"    (non-durable) non-exclusive queues by default (see the `RabbitMQ 4.3.0"},{"line_number":8,"context_line":"    release notes"},{"line_number":9,"context_line":"    \u003chttps://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0\u003e`__),"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"e57c861a_91778f68","line":6,"in_reply_to":"0929d97c_c166ebd6","updated":"2026-10-13 08:38:06.000000000","message":"should I notify other projects post-merge (but before doing a release) via the ML or should that happen pre-merge?","commit_id":"595eb9df474380357a9cdb77dc3c8f466fad8cf2"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@chainguard.dev","username":"toabctl"},"change_message_id":"a2ee12e0624ea7b171d63844b079bdd30ff7b617","unresolved":true,"context_lines":[{"line_number":3,"context_line":"  - |"},{"line_number":4,"context_line":"    The ``[oslo_messaging_rabbit] rabbit_quorum_queue`` and"},{"line_number":5,"context_line":"    ``[oslo_messaging_rabbit] rabbit_transient_quorum_queue`` options now"},{"line_number":6,"context_line":"    default to ``True``. RabbitMQ 4.3.0 refuses to create transient"},{"line_number":7,"context_line":"    (non-durable) non-exclusive queues by default (see the `RabbitMQ 4.3.0"},{"line_number":8,"context_line":"    release notes"},{"line_number":9,"context_line":"    \u003chttps://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0\u003e`__),"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"0929d97c_c166ebd6","line":6,"in_reply_to":"3a51cd35_a3b08e1c","updated":"2026-10-13 08:15:10.000000000","message":"PS6 adds a prelude (as the pika and ZeroMQ removals did), which renders at the top of the release, and opens the upgrade note with a warning admonition. Agreed on notifying the other projects too.","commit_id":"595eb9df474380357a9cdb77dc3c8f466fad8cf2"},{"author":{"_account_id":11583,"name":"Arnaud Morin","email":"arnaud.morin@gmail.com","username":"arnaudmorin"},"change_message_id":"b8aacc8fa3f258d1cb56b09ede4213d7457404ff","unresolved":true,"context_lines":[{"line_number":9,"context_line":"    \u003chttps://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0\u003e`__),"},{"line_number":10,"context_line":"    which is how the driver declared every RPC, notification, reply and"},{"line_number":11,"context_line":"    fanout queue with the previous defaults. Against RabbitMQ 4.3.0 and"},{"line_number":12,"context_line":"    later, creating those queues fails with ``(541) INTERNAL_ERROR - Feature"},{"line_number":13,"context_line":"    `transient_nonexcl_queues` is deprecated``. RabbitMQ\u0027s `list of"},{"line_number":14,"context_line":"    deprecated features"},{"line_number":15,"context_line":"    \u003chttps://www.rabbitmq.com/release-information/deprecated-features-list\u003e`__"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"b9b92783_d9e0a02d","line":12,"updated":"2026-10-13 08:11:05.000000000","message":"I don\u0027t think so much details is needed in the upgrade note. I\u0027d rather simplify it so operator really understand the stakes.","commit_id":"595eb9df474380357a9cdb77dc3c8f466fad8cf2"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@chainguard.dev","username":"toabctl"},"change_message_id":"da56def4801663247cab6d58b6dad07099e22f83","unresolved":false,"context_lines":[{"line_number":9,"context_line":"    \u003chttps://github.com/rabbitmq/rabbitmq-server/releases/tag/v4.3.0\u003e`__),"},{"line_number":10,"context_line":"    which is how the driver declared every RPC, notification, reply and"},{"line_number":11,"context_line":"    fanout queue with the previous defaults. Against RabbitMQ 4.3.0 and"},{"line_number":12,"context_line":"    later, creating those queues fails with ``(541) INTERNAL_ERROR - Feature"},{"line_number":13,"context_line":"    `transient_nonexcl_queues` is deprecated``. RabbitMQ\u0027s `list of"},{"line_number":14,"context_line":"    deprecated features"},{"line_number":15,"context_line":"    \u003chttps://www.rabbitmq.com/release-information/deprecated-features-list\u003e`__"}],"source_content_type":"text/x-yaml","patch_set":4,"id":"3c5bf2be_8bac2fde","line":12,"in_reply_to":"b9b92783_d9e0a02d","updated":"2026-10-13 08:13:50.000000000","message":"Done, cut it down to what changes, the migration, the incompatible options, how to keep the old behaviour, and use_queue_manager.","commit_id":"595eb9df474380357a9cdb77dc3c8f466fad8cf2"},{"author":{"_account_id":11583,"name":"Arnaud Morin","email":"arnaud.morin@gmail.com","username":"arnaudmorin"},"change_message_id":"237be3a8ada4b31178062382f952997fb74d7d53","unresolved":true,"context_lines":[{"line_number":53,"context_line":"    It keeps reply and fanout queue names stable across restarts, so quorum"},{"line_number":54,"context_line":"    queues are reused instead of being created under a new name on every"},{"line_number":55,"context_line":"    service start. It requires ``[oslo_concurrency] lock_path`` (or the"},{"line_number":56,"context_line":"    ``OSLO_LOCK_PATH`` environment variable) to be set."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"dd6d3b92_956e817d","line":56,"updated":"2026-10-13 08:12:40.000000000","message":"should we say this here? I think saying the option in config is enough","commit_id":"595eb9df474380357a9cdb77dc3c8f466fad8cf2"},{"author":{"_account_id":7102,"name":"Thomas Bechtold","email":"thomas.bechtold@chainguard.dev","username":"toabctl"},"change_message_id":"da56def4801663247cab6d58b6dad07099e22f83","unresolved":false,"context_lines":[{"line_number":53,"context_line":"    It keeps reply and fanout queue names stable across restarts, so quorum"},{"line_number":54,"context_line":"    queues are reused instead of being created under a new name on every"},{"line_number":55,"context_line":"    service start. It requires ``[oslo_concurrency] lock_path`` (or the"},{"line_number":56,"context_line":"    ``OSLO_LOCK_PATH`` environment variable) to be set."}],"source_content_type":"text/x-yaml","patch_set":4,"id":"178e038f_c28b6c1c","line":56,"in_reply_to":"dd6d3b92_956e817d","updated":"2026-10-13 08:13:50.000000000","message":"Done, dropped the lock_path sentence.","commit_id":"595eb9df474380357a9cdb77dc3c8f466fad8cf2"}]}