Skip to content

armgit / ODS

Public Imported from GitHub
0

ODS V3 Pre-Release: Public testing and refinement ahead of the official V3 launch. Turn your PC, Mac, or Linux box into a private AI server.

5.6 KB
Raw Blame

ODS OSS Launch Checklist

Date: 2026-03-02 Historical scope: March 2026 Strix Halo development checkout.

Archived checklist, not a current release gate. The completed/open labels below describe the original work session. Root and product license files and .env.example now exist. Current release acceptance is documented in Release Validation, the support matrix, and the September promotion record. Do not execute old workaround or launch instructions as a current runbook.

Completed This Session

P0: Must Fix Before OSS Launch

  1. Unify compose expectations across tests/scripts/docs ✅ Completed (2026-03-02)
  • Why: This repo uses docker-compose.base.yml + GPU overlays, but some tests/scripts had stale fallbacks.
  • Evidence:
  • Owner: Core Maintainer
  • Effort: M (0.5-1.5 days)
  • Exit criteria: CI/test scripts pass against Strix compose or support both compose files.
  1. Add and validate .env.example for reproducible installs ✅ Completed (2026-03-02)
  • Why: Tests expect it; migration script references it; the file was missing at the original review.
  • Evidence:
  • Owner: Core Maintainer
  • Effort: S (1-3 hours)
  • Exit criteria: .env.example committed and referenced variables validated by tests.
  1. Fix stale/missing doc links and path references ✅ Completed (2026-03-03)
  • Why: README/Quickstart had stale workflow references.
  • Owner: Docs Maintainer
  • Effort: S (1-2 hours)
  • Exit criteria: no broken local links in top-level docs.
  1. Add license file in this publishable repo root ✅ Completed (2026-03-02)
  • Why: the original checkout advertised Apache 2.0 before its license file was added. Current component terms are described in Licensing.
  • Owner: Maintainer/Legal
  • Effort: S (<1 hour)
  • Exit criteria: LICENSE present and matches stated license.
  1. Run launch smoke tests on a machine with Docker available
  • Why, at the original review: the work environment had no Docker CLI/daemon, so those observations did not verify runtime readiness.
  • Evidence:
    • scripts/ods-preflight.sh reports Docker not running.
    • scripts/ods-test.sh --quick fails early (docker not installed).
  • Owner: Release Engineer
  • Effort: S-M (2-4 hours)
  • Exit criteria: preflight + quick test pass on target host.

P1: Strongly Recommended Before/Right After Launch

  1. Split NVIDIA vs Strix docs or add clear command matrix
  • Why: mixed instructions (legacy llama-server and current llama-server:8080) create operator confusion.
  • Evidence:
  • Owner: Docs Maintainer
  • Effort: M (0.5-1 day)
  1. Modernize old docker-compose command style in docs
  • Why: docs mix docker-compose and docker compose; standardizing reduces support friction.
  • Evidence:
  • Owner: Docs Maintainer
  • Effort: S (1-2 hours)
  1. Refactor tests to mode-aware compose selection
  • Why: tests are currently tuned for legacy docker-compose.yml layouts.
  • Evidence:
  • Owner: QA/Infra
  • Effort: M-L (1-2 days)
  1. Add CI workflow for shell lint + test script syntax
  • Why: catches regressions like quoting/parser breaks pre-merge.
  • Owner: QA/Infra
  • Effort: M (0.5-1 day)

Suggested Launch Gate

Ship only after all P0 items are complete and the following command set is green on target hardware:

./scripts/ods-preflight.sh
./scripts/ods-doctor.sh
./scripts/ods-test.sh --quick
bash tests/test-phase-c-p1.sh