Skip to content

tracking: release-readiness against Dakota #71

Closed as not planned
Closed as not planned

Description

@mendezr
created_date: "2026-09-24"
document_status: draft
closed_date: null

Feature: 20260924190738-28eb0070-utah-release-readiness

Overview

Utah reaches releasable image and ISO quality with independently traceable package, desktop, upgrade and recovery evidence while preserving its Hummingbird bootc/RPM design. The linked Utah and Utah-packages issues remain the concrete audit slices rather than a second hidden backlog. Source: utah#71.

Requirements

  • Resolve linked release blockers
    Every linked P0/P1 Utah and Utah-packages slice is resolved or has an explicit maintainer-approved exception.
  • Gate the image on real behavior
    One immutable Utah image digest passes package, desktop, VM, installer, upgrade and rollback checks.
  • Prove offline installation
    A checksummed production ISO completes offline plain and encrypted installs.
  • Trace publication
    Testing/stable tags and ISO releases resolve to the exact tested image digest and originating workflow run.

Constraints

  • Utah retains Hummingbird bootc/RPM architecture; Dakota is reference for evidence/promotion practices, not a mandated stack change.
  • The source body contains literal escaped newlines; preserve and normalize all 21 task-list links when rewriting the issue.
  • Do not claim a linked issue completed merely because a label or old tracker text changed.

Acceptance Criteria

  • Resolve linked release blockers
    Each of the 21 linked issue URLs is accounted for as closed with evidence or an approved, documented exception.
  • Gate the image on real behavior
    Test results name the same digest and show each required lane completed.
  • Prove offline installation
    Both installation variants boot from the published ISO and match its published checksum.
  • Trace publication
    A reviewer follows image digest and workflow identity from passing gates through published tags and ISO artifacts.

Technical Approach

Success Metrics

  • One tested digest can be traced across image, ISO and publication gates without inconsistent source refs.

Non-Goals

  • No replatform to Dakota BuildStream, unapproved exception or placeholder release proof.

[You have received this identical output 5 times. Re-reading 'specs/speks/20260924190738-28eb0070-utah-release-readiness.md:raw' will not change it — use a narrower selector (path:A-B), or proceed with the edit.]

Activity

  1. mendezr commented on Sep 21, 2026

    @mendezr
    ContributorAuthor

    This is a tracking/umbrella issue: every acceptance criterion is the resolution of a linked sub-issue, which are tracked and worked individually across repo projectbluefin/utah and projectbluefin/utah-packages. There is no independent code deliverable attributable to issue #71 itself, so there is no PR to open against this issue. The actionable work lives in the sub-issues it links (utah #10–#23; utah-packages #19–#25), the large majority of which remain OPEN.

    Closed so far: utah #20, #22; utah-packages #20, #21, #22. Remaining open work must land via those sub-issues, not this tracking issue.

    — hive: backend=goose model=deepseek/deepseek-v4-flash-0731

    🐝 Hive Agent: contributor | SHA: 636b48e

  2. repires commented on Sep 22, 2026

    @repires
    Contributor

    This is an umbrella tracking issue for Utah release-readiness against Dakota. Every acceptance criterion is tracked through dedicated child issues and PRs across projectbluefin/utah and projectbluefin/utah-packages. There is no direct code deliverable or standalone PR attributable to issue #71 itself.

    Current status of linked audit slices and deferred packages:

    Actionable work is handled in these individual child issues and PRs rather than on this tracking issue.

    — hive: backend=agy

    🐝 Hive Agent: contributor | SHA: unknown

  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 6, 2026

    @hanthor
    Member

    Consolidated into #24: both umbrellas contain the same 21 linked audit slices and release acceptance criteria. #24 now has refreshed linked-issue checkboxes and remains open for the image/VM/installer/lifecycle/publication gates. This closes only the duplicate tracker, not any child issue or runtime acceptance requirement.

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

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions