Skip to content

tracking: close Utah release-readiness gaps against Dakota #24

Closed

Description

@hanthor

This was generated by AI during triage.

What to build

Type: HITL

Track the release-readiness work identified by the Utah/Bluefin/Dakota comparative audit. Dakota is the modern pipeline reference; Utah retains its Hummingbird bootc/RPM architecture while adopting Dakota's evidence, promotion, ISO, and recovery practices.

Audit slices

Existing deferred-package issues

Acceptance criteria

  • Every linked P0/P1 slice is resolved or has an explicit maintainer-approved exception.
  • A Utah image digest passes package, desktop, VM, installer, upgrade, and rollback gates.
  • A checksummed production ISO passes offline plain and encrypted installation gates.
  • Moving testing/stable tags and published ISO artifacts can be traced to the exact tested digest and workflow run.

Blocked by

The unchecked audit slices above and the acceptance gates remain open.

This is the canonical release-readiness umbrella; #71 duplicates these same
21 issue links and acceptance criteria and has been consolidated here.
Checked links reflect current GitHub closure, not new runtime acceptance proof.

Activity

  1. mrbobbytables commented on Sep 22, 2026

    @mrbobbytables
    Contributor

    This is an umbrella tracking issue (Type: HITL) tracking release-readiness work across 17 audit slices and 4 deferred-package issues in projectbluefin/utah and projectbluefin/utah-packages.

    Actionable work items are partitioned into and driven by their dedicated child issues and PRs:

    Because this issue is a meta-tracking issue requiring all constituent P0/P1 audit slices and full pipeline promotion gates to resolve, there is no direct shippable change for issue #24 itself in this repository.

    — hive: backend=copilot model=gemini-3.8-flash

    🐝 Hive Agent: contributor | SHA: unknown

  2. repires commented on Sep 23, 2026

    @repires
    Contributor

    This is an umbrella tracking issue (Type: HITL) tracking release-readiness work across 17 audit slices and 4 deferred-package issues in projectbluefin/utah and projectbluefin/utah-packages. There is no direct code deliverable or standalone PR attributable to issue #24 itself.

    Current status of linked audit slices and deferred packages:

    Actionable work items are handled in their dedicated child issues and PRs.

    — hive: backend=agy

    🐝 Hive Agent: contributor | SHA: 335f9a0

  3. hivecommons-hive commented on Oct 1, 2026

    @hivecommons-hive
    Contributor

    What to reply

    • /hive approve: go with the recommendation
    • /hive decision <your instructions>: go ahead, following your instructions
    • /hive help: show these again

    If this issue is waiting only for reporter confirmation after a merged fix, the reporter or a maintainer can reply /fixed instead.

    Only a maintainer with write access can un-park; everything else is ignored. Full command reference: https://github.com/hivecommons/hive/blob/v5/src/docs/maintainer-commands.md.

  4. hanthor commented on Oct 12, 2026

    @hanthor
    MemberAuthor

    Maintainer decision: #24 is a release-readiness umbrella, not a pending policy choice. Its remaining work is tracked by the dedicated child issues and acceptance gates; no further human decision is needed to start those slices. I am removing the stale needs-decision label and marking the umbrella blocked while its technical/runtime gates remain open. This does not satisfy or close the release-readiness acceptance criteria.

  5. added
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    and removed on Oct 12, 2026
  6. added
    hive/likely-doneHive verified that a merged PR references or claims this issue; pending confirmation
    on Oct 13, 2026
  7. removed
    triage/acceptedScope accepted; ready for work. Use `/triage accepted`.
    on Oct 13, 2026
  8. github-actions commented on Oct 13, 2026

    @github-actions
    Contributor

    To accept this issue, comment /triage accepted. To categorize, comment /area <area> or /kind <kind>.

  9. hivecommons-hive commented on Oct 13, 2026

    @hivecommons-hive
    Contributor

    Fixed by #198 (merged e3d35d6). Closing. Reply /reopen if the problem persists.

  10. removed
    blockedWaiting on something outside this repository. Use `/label blocked` or `/remove-label blocked`.
    on Nov 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions