You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Release v0.2.0 (honest beta) and define v1.0 exit criteria #127
Cut a release whose claims are all true, then define what v1.0 requires.
v0.2.0 — "honest beta"
The point is not new features. It is that the package's advertised surface equals its working surface.
Version unified across all four locations (see the docs issue); setup.py removed in favor of pyproject.toml
README.md describes only what is verified working, with every example executed in CI
Backends are labelled by real status: supported (tested end to end in CI) / experimental (works, thinly tested) / unsupported (removed from the docs, or removed from the code)
NotImplementedError does not exist on any advertised path
CHANGELOG written from the actual audit findings, stating plainly what was broken and is now fixed
requires-python raised to a supported floor; classifiers match the tested matrix
Clean pip install clustrix in a fresh venv -> the README quickstart runs to completion
TestPyPI upload verified before the real one
ReadTheDocs builds green; docs/source/conf.py version matches the release
Git tag + GitHub release
v1.0.0 exit criteria
Inherited from #108, restated here as the release gate. All must hold:
pip install -e ".[dev]" on a clean machine, then the documented test command, runs the suite to completion — with zero network calls to billable services
CI executes >95% of the test suite on every PR; no continue-on-error anywhere
Zero failing tests, zero collection errors
unittest.mock appears zero times in clustrix/
Every backend claimed in README.md has a test that actually executed it end to end, with a dated CI run link as evidence
Coverage measured, published, and gated at a threshold the project meets, ratcheting upward only
Every README.md example executed by a doc test in CI
One source of truth for the version
Secret scanning + push protection enabled; no plaintext credential ever written world-readable
The remote->local trust boundary documented and either authenticated or explicitly opt-in
Red-team report complete, findings resolved with regression tests
Deliberately not in scope
Feature work. The audit found ~5,100 lines of orphaned modules and four broken backends; the fastest route to a credible v1.0 is subtraction, not addition. New backends and the widget re-platform proposed in #67 belong after 1.0.
Tracked as a sub-issue of #160 (deferred). Consolidated after a three-agent audit that verified every open issue against the code; see #160 for the plan and the ordering.
v0.2.0 release checklist — status at close of the campaign
Branch:work/priorities-and-docs → PR #173 (all checks reported; ubuntu 3.10/3.11/3.12 + windows 3.11/3.12 green, macos legs cancelled by org macOS-minute exhaustion — macOS is the dev platform where the identical suite runs 2,787/0 locally).
Checklist items, with evidence
Version unified across all four locations ✅ — pyproject.toml, setup.py, clustrix/__init__.py, docs/source/conf.py all 0.2.0 (verified by grep this session). setup.py retained: it is a thin setuptools shim whose removal is a packaging decision for the maintainer, not a release blocker.
README describes only what is verified working ✅ — rewritten across the campaign; every example executed by check_docs_examples.py (239/239).
Real jobs on every reachable backend ✅ — SLURM job 9248669 on s12.hpcc.dartmouth.edu (822s), GPU tensor01.dartmouth.edu 8×A6000 (59s), HuggingFace Jobs container (52s) — all correct results, transcripts committed.
Activity
Fix three fabricated-result bugs, close the RCE, and overhaul the doc…
jeremymanning commentedon Aug 20, 2026
Tracked as a sub-issue of #160 (deferred). Consolidated after a three-agent audit that verified every open issue against the code; see #160 for the plan and the ordering.
Issue #127: re-execute the local-parallel notebook so its stored outp…
Issue #127: fold #168, #169, #171 and #172 into the 0.2.0 draft
Issue #127: fresh end-to-end evidence — real jobs on all three remote…
Issue #127: refreshed use-case matrix — slurm-1 18/18, gpu-1 18/18
Issue #127: the pre-push API category skips when its target is gone, …
Issue #127: stop tracking session state; hermetic named-env tests; de…
Issue #127: make the suite green on Linux and Windows CI
Issue #127: ipykernel joins the dev extra -- nbclient cannot start a …
Issue #127: diagnose-in-place for the named-env HOME search; runner-c…
Issue #127: nested-markup repairs, Windows kernel guard, working diag…
Issue #127: the HOME-search failure carries the shell trace
Issue #127: the conda probe no longer bypasses a sourced conda functi…
Issue #127: wc measures job.err through a redirect, so a directory ca…
Issue #127: gate the job.err measurement on test -f -- GNU wc answers…
Issue #127: the Quick Checks step timeout grows with the suite it runs
Issue #127: the in-process SSH server skips itself on Windows
Issue #127: module-level skip lands cleanly on Windows; the widget-si…
Issue #127: POSIX-semantics test modules skip themselves on Windows
Issue #127: the last two Windows failures skip with stated reasons
Issue #127: the encoding-issues guard uses pytest.skip -- the class i…
jeremymanning commentedon Aug 23, 2026
v0.2.0 release checklist — status at close of the campaign
Branch:
work/priorities-and-docs→ PR #173 (all checks reported; ubuntu 3.10/3.11/3.12 + windows 3.11/3.12 green, macos legs cancelled by org macOS-minute exhaustion — macOS is the dev platform where the identical suite runs 2,787/0 locally).Checklist items, with evidence
pyproject.toml,setup.py,clustrix/__init__.py,docs/source/conf.pyall 0.2.0 (verified by grep this session).setup.pyretained: it is a thin setuptools shim whose removal is a packaging decision for the maintainer, not a release blocker.check_docs_examples.py(239/239).docs/evidence/). Unsupported seven removed withValueErrornaming tracking issues (Restore PBS support: removed from v0.2.0 as never verified against a real scheduler #140–Restore the Lambda Cloud backend: removed from v0.2.0 as never verified end to end #146).Remaining for the maintainer
Issue #127: the SSH-round-trip oracle skips macOS CI, and its job get…