)]}'
{".zuul.yaml":[{"author":{"_account_id":11604,"name":"sean mooney","email":"smooney@redhat.com","username":"sean-k-mooney"},"change_message_id":"bc00ac357cf673e8e0f0d3044d8cfba11994b504","unresolved":true,"context_lines":[{"line_number":10,"context_line":"        - cyborg-tempest-2026-2"},{"line_number":11,"context_line":"        - cyborg-tempest-2026-1"},{"line_number":12,"context_line":"        - cyborg-tempest-2025-2"},{"line_number":13,"context_line":"        - cyborg-tempest-2025-1"},{"line_number":14,"context_line":"        - cyborg-tempest-ipv6"},{"line_number":15,"context_line":"    gate:"},{"line_number":16,"context_line":"      jobs:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"794ae94c_c1d5ed62","line":13,"range":{"start_line":13,"start_character":0,"end_line":13,"end_character":31},"updated":"2026-09-21 16:19:58.000000000","message":"we should really drop the oldes job when adding the new one.\n\ni have some chagnes in the gate that it conclict with but once those merge we cna proceed with this but i genreally prefer not to split the addtion and removal into two patches.","commit_id":"a86b496de0786083dd2f9eccbc69475b35d1a111"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"2d65d600b23cc71c87f504309e23b3f19bcc959f","unresolved":true,"context_lines":[{"line_number":10,"context_line":"        - cyborg-tempest-2026-2"},{"line_number":11,"context_line":"        - cyborg-tempest-2026-1"},{"line_number":12,"context_line":"        - cyborg-tempest-2025-2"},{"line_number":13,"context_line":"        - cyborg-tempest-2025-1"},{"line_number":14,"context_line":"        - cyborg-tempest-ipv6"},{"line_number":15,"context_line":"    gate:"},{"line_number":16,"context_line":"      jobs:"}],"source_content_type":"text/x-yaml","patch_set":2,"id":"6235ca67_5d4b7325","line":13,"range":{"start_line":13,"start_character":0,"end_line":13,"end_character":31},"in_reply_to":"794ae94c_c1d5ed62","updated":"2026-09-21 16:25:02.000000000","message":"2025.1 still remains maintained for additional weeks ( Unmaintained estimated 2026-10-02 ), and I think we should not remove this job until then. That\u0027s the timing gap we always have around the release timing.","commit_id":"a86b496de0786083dd2f9eccbc69475b35d1a111"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":8556,"name":"Ghanshyam Maan","display_name":"Ghanshyam Maan","email":"gmaan.os14@gmail.com","username":"ghanshyam"},"change_message_id":"0f736ca1619400f07749a91685bd8214f14d89d9","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"9940722b_cb10e557","updated":"2026-09-11 18:14:49.000000000","message":"It\u0027s not the correct time to start stable/2026.2. They do not test; they meant to, so this will be an extra job, unnecessarily consuming the CI and testing the master only.\n\nOnce QA setup the tooling for stable/2026.2 then only we should add these jobs","commit_id":"41093ce3b0624f7234553f57a3bc8a4952676782"},{"author":{"_account_id":9816,"name":"Takashi Kajinami","email":"kajinamit@oss.nttdata.com","username":"kajinamit"},"change_message_id":"7684d99f0b14586cd69d8e8af0fe57a68857255a","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":1,"id":"202f6b95_c006a2e8","in_reply_to":"9940722b_cb10e557","updated":"2026-09-12 08:58:41.000000000","message":"\u003e testing the master only.\n\nI might be wrong but isn\u0027t that specific to devstack ? AFAIK devstack does not define jobs per stable branches, so the appropriate stable branch should be selected at least for the service projects.\n\nI\u0027m ok to delay merging this anyway, but I personally prefer merging such job update asap, because of the past fact that multiple projects failed to add the required stable branches quote often.","commit_id":"41093ce3b0624f7234553f57a3bc8a4952676782"}]}