)]}'
{"/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":"d4608ead3f4d955adaf319f7e0743c2bc4e016f4","unresolved":false,"context_lines":[{"line_number":1,"context_line":"Parent:     7f137a06 (Move 2026.2 RBAC spec to implemented)"},{"line_number":2,"context_line":"Author:     Chandan \u003cchkumar@redhat.com\u003e"},{"line_number":3,"context_line":"AuthorDate: 2026-09-15 17:27:57 +0530"},{"line_number":4,"context_line":"Commit:     Chandan \u003cchkumar@redhat.com\u003e"}],"source_content_type":"text/x-gerrit-commit-message","patch_set":3,"id":"b862d3b0_5b6a085c","line":1,"updated":"2026-09-15 14:18:09.000000000","message":"The 2027.1 spec template requires that specifications proposing REST API changes add the APIImpact flag to the commit message so they remain queryable in Gerrit (message:apiimpact). This spec proposes a new microversion, a device_state response field, and the new admin-only POST /v2/devices/{uuid}/clean endpoint. The original 2026.2 commit of this same spec (b6c43f7) included an APIImpact line; this repropose commit omits it.\n\n**Severity**: SUGGESTION | **Confidence**: 0.9\n\n**Impact**: The repropose loses the Gerrit queryability the project uses to track API-impacting specs, breaking the cross-project traceability the template establishes for a change that adds an admin-only endpoint and a microversion.\n\n**Recommendation**:\nAdd an APIImpact line to the commit message, as the original 2026.2 commit did, when the patch is next reworked, restoring queryability for API reviewers.","commit_id":"22923863a710eec48455020dbf47a2e204223403"}],"specs/2027.1/approved/generic-nvme-driver-with-secure-cleanup.rst":[{"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":"4df333a7dc994c7089c38524cd8695fe3be10e98","unresolved":false,"context_lines":[{"line_number":944,"context_line":"Driver documentation will include examples of how to manage Inspur"},{"line_number":945,"context_line":"devices with the new generic driver."},{"line_number":946,"context_line":""},{"line_number":947,"context_line":"This release introduces N-1 agent compatibility. A 2026.2 conductor"},{"line_number":948,"context_line":"and API can operate with 2026.1 agents. The conductor checks"},{"line_number":949,"context_line":"``can_send_version(\u00271.1\u0027)`` before dispatching ``cleanup_device``"},{"line_number":950,"context_line":"(see RPC API impact section). For non-NVMe devices, the conductor"}],"source_content_type":"text/x-rst","patch_set":2,"id":"3334f0c5_379cfd75","line":947,"updated":"2026-09-15 12:20:58.000000000","message":"The spec is re-proposed for 2027.1 with Phase 1 marked done in 2026.2, but the RPC, REST, and upgrade sections still describe the N-1 compatibility boundary using releases from the original 2026.2 target. Line 947 states \u0027This release introduces N-1 agent compatibility. A 2026.2 conductor and API can operate with 2026.1 agents\u0027; line 815 calls an agent lacking RPC version 1.1 \u0027a 2026.1 agent\u0027; line 762 says the clean endpoint returns 400 for a \u0027pre-2026.2 agent\u0027. Because the cleanup_device RPC bump (1.0 -\u003e 1.1), the microversion, and the POST /clean endpoint are future 2027.1 work items (Phases 3 and 5), the old-agent boundary when the feature lands is a 2026.2 agent, not a 2026.1 agent.\n\n**Severity**: WARNING | **Confidence**: 0.82\n\n**Impact**: Implementers of the can_send_version guard, and writers of upgrade docs and API error text derived from this spec, will state the wrong conductor/agent release pairing (2026.2 conductor with 2026.1 agents instead of 2027.1 conductor with 2026.2 agents). \u0027This release\u0027 also becomes ambiguous, which can mislead release-note and compatibility matrix authors.\n\n**Suggestion**:\nUpdate the compatibility references for the 2027.1 target: state that the 2027.1 conductor and API operate with 2026.2 agents; change \u0027(a 2026.1 agent)\u0027 at line 815 to a 2026.2 agent and \u0027(pre-2026.2 agent)\u0027 at line 762 to \u0027(pre-2027.1 agent)\u0027 or equivalent; and clarify that \u0027This release\u0027 at line 947 is 2027.1.","commit_id":"5d8ef2609c21df2cb9a8e0f4a7a0ca1673c4edf3"},{"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":"4df333a7dc994c7089c38524cd8695fe3be10e98","unresolved":false,"context_lines":[{"line_number":972,"context_line":"Work Items"},{"line_number":973,"context_line":"----------"},{"line_number":974,"context_line":""},{"line_number":975,"context_line":"**Phase 1 — Foundation (independent patches) Done in 2026.2 :**"},{"line_number":976,"context_line":""},{"line_number":977,"context_line":"* Alembic migration for nullable ``device_state`` column and ``NVME``"},{"line_number":978,"context_line":"  type. Bump ``Device`` object version to ``1.3`` with"}],"source_content_type":"text/x-rst","patch_set":2,"id":"78761978_e2de0f2f","line":975,"updated":"2026-09-15 12:20:58.000000000","message":"Line 975 reads \u0027**Phase 1 — Foundation (independent patches) Done in 2026.2 :**\u0027. The completion status is appended without punctuation and there is a stray space before the colon, so the heading reads awkwardly. The 2026.2 copy of the spec used the clean heading \u0027**Phase 1 — Foundation (independent patches):**\u0027.\n\n**Severity**: SUGGESTION | **Confidence**: 0.9\n\n**Impact**: Minor readability defect in a permanent heading of an approved spec; the appended status also mixes plan state into the phase title rather than the history table that already records it.\n\n**Recommendation**:\nRewrite the heading as \u0027**Phase 1 — Foundation (independent patches, done in 2026.2):**\u0027 or move the status note to a sentence under the heading, since the history table already records the 2026.2 acceptance.","commit_id":"5d8ef2609c21df2cb9a8e0f4a7a0ca1673c4edf3"},{"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":"d4608ead3f4d955adaf319f7e0743c2bc4e016f4","unresolved":false,"context_lines":[{"line_number":944,"context_line":"Driver documentation will include examples of how to manage Inspur"},{"line_number":945,"context_line":"devices with the new generic driver."},{"line_number":946,"context_line":""},{"line_number":947,"context_line":"This release introduces N-1 agent compatibility. A 2026.2 conductor"},{"line_number":948,"context_line":"and API can operate with 2026.1 agents. The conductor checks"},{"line_number":949,"context_line":"``can_send_version(\u00271.1\u0027)`` before dispatching ``cleanup_device``"},{"line_number":950,"context_line":"(see RPC API impact section). For non-NVMe devices, the conductor"}],"source_content_type":"text/x-rst","patch_set":3,"id":"0e9abde2_35440e7f","line":947,"updated":"2026-09-15 14:18:09.000000000","message":"The spec is re-targeted from 2026.2 to 2027.1 (commit subject, history row \u00272027.1 Reproposed\u0027, Phase 1 marked \u0027done in 2026.2\u0027), but several release-version statements still describe the 2026.2 cycle. The upgrade section says \u0027This release introduces N-1 agent compatibility. A 2026.2 conductor and API can operate with 2026.1 agents\u0027; the REST error-code list scopes the 400 response to a \u0027pre-2026.2 agent\u0027; and the RPC section calls an agent lacking RPC 1.1 \u0027a 2026.1 agent\u0027. Because RPC 1.1 and the clean endpoint land with this spec in 2027.1, agents without RPC 1.1 are 2026.2-and-older, and this release\u0027s N-1 compatibility is a 2027.1 conductor/API operating with 2026.2 agents.\n\n**Severity**: WARNING | **Confidence**: 0.9\n\n**Impact**: Implementers and operators reading the 2027.1 spec get the previous cycle\u0027s compatibility matrix: the documented N-1 upgrade path and the 400-error condition for POST /v2/devices/{uuid}/clean describe release combinations that do not match this feature\u0027s landing release, which misleads upgrade planning and implementation of the can_send_version guard. The unchanged 2027.2 dates also quietly halve the intended deprecation and nullable-column windows.\n\n**Suggestion**:\nRe-baseline the release references for 2027.1: \u0027A 2027.1 conductor and API can operate with 2026.2 agents\u0027 (upgrade section), \u0027(pre-2027.1 agent)\u0027 in the error-code list, \u0027(a 2026.2 agent)\u0027 in the RPC section, and re-confirm the contract-migration and driver-removal target dates (currently both 2027.2) now that the feature lands one release later.","commit_id":"22923863a710eec48455020dbf47a2e204223403"}]}