)]}'
{"/COMMIT_MSG":[{"author":{"_account_id":28006,"name":"teim-ci","display_name":"teim-ci","email":"ci@seanmooney.info","username":"ci-sean-mooney","status":"this is a third-party ci account run by sean-k-mooney on irc\nhosted at zuul.teim.app"},"tag":"autogenerated:zuul:automatic-ci","change_message_id":"f9fce089c20107ab12b05f0ac72f5e9f89f050ce","unresolved":false,"context_lines":[{"line_number":1,"context_line":"Parent:     815ed72b (Merge \"Add 2027.1 spec structure\")"},{"line_number":2,"context_line":"Author:     jgilaber \u003cjgilaber@redhat.com\u003e"},{"line_number":3,"context_line":"AuthorDate: 2026-09-07 16:43:45 +0200"},{"line_number":4,"context_line":"Commit:     jgilaber \u003cjgilaber@redhat.com\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":2,"id":"09041905_714c2b20","line":1,"updated":"2026-09-07 17:41:58.000000000","message":"The commit message says the change moves the two specs from approved to implemented and adds redirect entries. The actual diff also deletes the template.rst symlinks in specs/2026.2/approved/ and specs/2026.2/implemented/ (both pointed to ../../2026.2-template.rst). These deletions are not described anywhere in the message and deviate from the sibling 2027.1 cycle, whose approved/ and implemented/ directories still carry template.rst symlinks added one commit earlier in ce5bdbe.\n\n**Severity**: WARNING | **Confidence**: 0.85\n\n**Impact**: No functional or doc-build breakage: the 2026.2 template remains reachable via doc/source/specs/2026.2/template.rst and the top-level specs/2026.2-template.rst. However, reviewers cannot tell whether the symlink removal is intentional; it makes the 2026.2 cycle layout inconsistent with 2027.1, and a contributor adding a late 2026.2 spec no longer finds the template inside specs/2026.2/approved/.\n\n**Suggestion**:\nEither restore the two template.rst symlinks to keep the per-cycle convention used in 2027.1, or keep the deletion but document it in the commit message (e.g. \u0027Remove template.rst symlinks from 2026.2 approved/ and implemented/ now that the cycle is closing\u0027) so the removal is reviewable as deliberate.","commit_id":"8fb447a751e2e9bcbd841ab4fa6939d2f1578847"}],"/PATCHSET_LEVEL":[{"author":{"_account_id":30002,"name":"Douglas Viroel","email":"viroel@gmail.com","username":"dviroel"},"change_message_id":"43d350bbcd584f9b71f2d13fe89f0d7cef673579","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"06424da8_cb3b6879","updated":"2026-09-10 13:59:21.000000000","message":"lgtm, unless you want to update the openstack-sdk to remove the piece  that wasn\u0027t merged","commit_id":"8fb447a751e2e9bcbd841ab4fa6939d2f1578847"},{"author":{"_account_id":12393,"name":"chandan kumar","display_name":"Chandan Kumar","email":"chkumar@redhat.com","username":"chkumar246"},"change_message_id":"2ff68a35a7bee87433b0d4d6703f300ba79bb560","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"4c79add4_5558ac3e","updated":"2026-09-10 13:08:37.000000000","message":"yup, we can mark improve watcher dashboard ui testing done. New tests will get added as we add more features.","commit_id":"8fb447a751e2e9bcbd841ab4fa6939d2f1578847"},{"author":{"_account_id":34452,"name":"Joan Gilabert","display_name":"jgilaber","email":"jgilaber@redhat.com","username":"jgilaber"},"change_message_id":"f99f0b6999435af3bed04e5d2ecd902fe9fdd42e","unresolved":false,"context_lines":[],"source_content_type":"","patch_set":2,"id":"6b80123d_ddcf3d8f","in_reply_to":"06424da8_cb3b6879","updated":"2026-09-15 15:25:37.000000000","message":"I plan to repropose that part for next cycle so I think the sdk spec is ok as is, unless other people object to marking it as implemented","commit_id":"8fb447a751e2e9bcbd841ab4fa6939d2f1578847"}]}