)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"21e6bd3abc1c186a30ccc51394f6b4c675e0fd52","unresolved":true,"context_lines":[{"line_number":4,"context_line":"Commit:     Dmitriy Chubinidze \u003cdcu995@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2025-05-25 17:48:09 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Convert to uppercase policy level"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Minor fix converting policy level naming to uppercase"},{"line_number":10,"context_line":"for overall consistency."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":9,"id":"102d56ee_ea419b3d","line":7,"range":{"start_line":7,"start_character":21,"end_line":7,"end_character":33},"updated":"2026-02-08 07:12:03.000000000","message":"We don\u0027t have to fix this now unless we get any other points, but L7 does not indicate policy level, but the protocol layer to which the policy is applied...","commit_id":"c7b1e061f5d61be92236d2160d0abcaa9379ad8f"},{"author":{"_account_id":37632,"name":"Dmitriy Chubinidze","email":"dcu995@gmail.com","username":"chubinidzedr"},"change_message_id":"a35228799f6834b80ad24722b0737116a58f712a","unresolved":false,"context_lines":[{"line_number":4,"context_line":"Commit:     Dmitriy Chubinidze \u003cdcu995@gmail.com\u003e"},{"line_number":5,"context_line":"CommitDate: 2025-05-25 17:48:09 +0000"},{"line_number":6,"context_line":""},{"line_number":7,"context_line":"Convert to uppercase policy level"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"Minor fix converting policy level naming to uppercase"},{"line_number":10,"context_line":"for overall consistency."}],"source_content_type":"text/x-gerrit-commit-message","patch_set":9,"id":"6f166faf_342d1811","line":7,"range":{"start_line":7,"start_character":21,"end_line":7,"end_character":33},"in_reply_to":"102d56ee_ea419b3d","updated":"2026-02-08 23:33:20.000000000","message":"Thanks for pointing, made some corrections.","commit_id":"c7b1e061f5d61be92236d2160d0abcaa9379ad8f"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"d224274bfdca392ba4c2114f63b53e0a92503f6d","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":7,"id":"085c4ff0_03892007","updated":"2025-05-25 16:04:06.000000000","message":"LGTM","commit_id":"9a96fcd0f149d1ede054c888ffbcfaf94a6e0a39"},{"author":{"_account_id":37598,"name":"Ivan Anfimov","display_name":"Ivan Anfimov","email":"lazekteam@gmail.com","username":"anfimovir"},"change_message_id":"856c38d65ea94f299f2af107bcdc8f4ff7b07714","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"82fccc57_0bf39d18","updated":"2026-02-06 21:02:22.000000000","message":"@gthiemon@redhat.com hello, I think we can merge this MR for provide time translations teams update translations until release.","commit_id":"c7b1e061f5d61be92236d2160d0abcaa9379ad8f"},{"author":{"_account_id":11628,"name":"Michael Johnson","email":"johnsomor@gmail.com","username":"johnsom"},"change_message_id":"bdc7bd272e95206f85c9dcda8e8d00be5633404a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"7e3ec77e_af15af80","updated":"2025-10-22 19:12:08.000000000","message":"I am ok with this and I think the i18n impact will be low as the strings are reused.","commit_id":"c7b1e061f5d61be92236d2160d0abcaa9379ad8f"},{"author":{"_account_id":29244,"name":"Gregory Thiemonge","email":"gthiemon@redhat.com","username":"gthiemonge"},"change_message_id":"5583453f97065dfd96a9903bd07485c600917476","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"b7bcffb4_1915efbb","updated":"2025-05-26 06:42:20.000000000","message":"I\u0027m a bit puzzled with these changes\nit breaks the translation strings for many languages\n\nand the funny thing is that this uppercase change is correctly handled in the en_GB locale:\nhttps://github.com/openstack/octavia-dashboard/blob/890ed461f27740d3e6893c0cfbeb50d530dd720c/octavia_dashboard/locale/en_GB/LC_MESSAGES/djangojs.po#L1458","commit_id":"c7b1e061f5d61be92236d2160d0abcaa9379ad8f"},{"author":{"_account_id":37632,"name":"Dmitriy Chubinidze","email":"dcu995@gmail.com","username":"chubinidzedr"},"change_message_id":"a67b3324833f07ef95195e5a86a74caaced6c26e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":9,"id":"6840be7b_401fb087","in_reply_to":"b7bcffb4_1915efbb","updated":"2025-05-26 07:54:25.000000000","message":"@gthiemon@redhat.com  \nHi, Gregory.\nThanks for feedback,I understand your concerns about the impact on translation strings. However, the updates were made to correct inaccuracies in the original English phrases, I see no way to fix those without modifying the source strings. This kind of change is a common and accepted practice across many projects — including OpenStack-Ansible, Horizon, and others — whenever original phrasing is incorrect or misleading.","commit_id":"c7b1e061f5d61be92236d2160d0abcaa9379ad8f"}]}
