)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":15343,"name":"Tim Burke","email":"tburke@nvidia.com","username":"tburke"},"change_message_id":"1e81e36379ec075404e1dacace9aeef51e8fdae3","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"[stable-only][CI] Remove jobs against EOL branches"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"victoria, wallaby and xena moved to End of Life recently. Let\u0027s do a"},{"line_number":10,"context_line":"clean up and remove related old rolling upgrade jobs."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I64a2027b298542cc91c93b2fc912b35f80587c12"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"07398a72_7226c4e4","line":9,"range":{"start_line":9,"start_character":0,"end_line":9,"end_character":8},"updated":"2026-01-29 05:07:13.000000000","message":"No longer part of the change.\n\n...which in turn also means the zuul config error is resolved. What\u0027s the impetus now? Just because a branch is EOL doesn\u0027t mean everyone has upgraded off it, and I know I\u0027d prefer to recommend upgrading straight to latest rather than maintain (and walk users through) some DAG of upgrade paths.\n\nI\u0027d be more understanding if this was part of the regular check pipeline, but I intentionally push these off to be on-demand things, usually only run as part of a release -- so what\u0027s the harm in keeping them?\n\nSeparately, why stable-only? If we really want to drop them, why not [start from master](https://github.com/openstack/swift/blob/2.37.0/.zuul.yaml#L755-L756)?","commit_id":"af4a05617a6504b13a9e3137e015b6c92a51ff3c"},{"author":{"_account_id":17685,"name":"Elod Illes","email":"elod.illes@est.tech","username":"elod.illes"},"change_message_id":"115237566ea6588e823d751f27af7d83e3fb5879","unresolved":true,"context_lines":[{"line_number":6,"context_line":""},{"line_number":7,"context_line":"[stable-only][CI] Remove jobs against EOL branches"},{"line_number":8,"context_line":""},{"line_number":9,"context_line":"victoria, wallaby and xena moved to End of Life recently. Let\u0027s do a"},{"line_number":10,"context_line":"clean up and remove related old rolling upgrade jobs."},{"line_number":11,"context_line":""},{"line_number":12,"context_line":"Change-Id: I64a2027b298542cc91c93b2fc912b35f80587c12"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"2c03dc32_1486947c","line":9,"range":{"start_line":9,"start_character":0,"end_line":9,"end_character":8},"in_reply_to":"07398a72_7226c4e4","updated":"2026-01-29 10:05:12.000000000","message":"First of all, thanks Tim for checking the patch!\n\nThe original intention was to eliminate the zuul config error, which was caused by the victoria job (which was already deleted from newer branches), but you are right, the wallaby and xena jobs should be deleted first from the master then from the newer stable branches.\n\nOtherwise, the deletion of the zuul job definitions of wallaby and xena jobs is just a clean up, but i\u0027m not insisting on deleting them. (I always thought like people who are interested on these jobs, can simply revert the relevant change themselves.)\n\nBut as you say, now the zuul config error is fixed, so I\u0027ll abandon this now.","commit_id":"af4a05617a6504b13a9e3137e015b6c92a51ff3c"}]}