)]}'
{"/PATCHSET_LEVEL":[{"author":{"_account_id":15334,"name":"Stephen Finucane","display_name":"stephenfin","email":"stephenfin@redhat.com","username":"sfinucan"},"change_message_id":"607368a1094a2a53e229261263801e0de6f495bc","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"741c0ec4_5f5d218b","updated":"2026-04-24 16:50:50.000000000","message":"I am not in favor of this option. I believe we have a serious issue and the status quo is not working. We need to try something.","commit_id":"016909f39599ac572009d2578da89360744cfd06"},{"author":{"_account_id":9708,"name":"Balazs Gibizer","display_name":"gibi","email":"gibizer@gmail.com","username":"gibi"},"change_message_id":"a4a0948893682ab380061f57195936f14bcbe247","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"25ce396c_bfc1f096","updated":"2026-04-28 14:47:35.000000000","message":"I rather try another option, fail and roll back or adjust that option. For a long time we went with this status quo and it is resulted in constant review bandwidth limits. Some limits are good to keep the amount of changes sane, but I think we reached the point where the limits are actually preventing useful and good code to land or land in time. I think trying something and learning from it is better than staying still.","commit_id":"016909f39599ac572009d2578da89360744cfd06"}]}