Release: v1.0 readiness checklist

[jaharris87]

Release: v1.0 readiness checklist

This umbrella tracks the v1.0 readiness checklist for moving fTimer from pre-1.0 to v1.0.

Context

Current release docs, installed API docs, and package probes still describe the pre-1.0 / 0.2.x compatibility boundary. Before v1.0, maintainers need an explicit 1.x compatibility and support policy, refreshed release evidence, and a release-prep closeout that keeps support claims inside the validated matrix.

Key source-of-truth files to read first:

• AGENTS.md
• README.md
• docs/release.md
• docs/release-evidence.md
• docs/installed-api.md
• docs/semantics.md
• docs/openmp-timing-modes.md
• docs/csv-schema.md
• docs/documentation-audience.md
• docs/maintainer.md
• docs/workflows/pr-open.md
• docs/workflows/review-monitoring.md
• docs/workflows/findings-disposition.md
• CONTRIBUTING.md

Release-blocking checklist IDs

• V1-RB-01: Define the v1.0 / 1.x compatibility promise. Tracked by Strategic question: define fTimer 1.x compatibility and support policy #349 and Feature: update v1.0 package version behavior and installed-consumer probes #350.
• V1-RB-02: Freeze or narrow the stable public API before 1.0. Tracked by Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351.
• V1-RB-03: Decide which user-facing formats are stable in 1.0. Tracked by Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351.
• V1-RB-04: Reconcile README claims with release evidence for v1.0. Tracked by Feature: refresh v1.0 release claims and evidence #352.
• V1-RB-05: Triage deferred/non-goal items for v1.0. Tracked by Feature: refresh v1.0 release claims and evidence #352.
• V1-RB-06: Decide MPICH MPI+OpenMP evidence level for v1.0. Tracked by Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353.
• V1-RB-07: Prepare v1.0 release process, artifacts, and notes. Tracked by Feature: prepare v1.0 release notes, validation record, and artifact closeout #354.
• V1-RB-08: Define 1.x support/security/post-release policy. Tracked by Strategic question: define fTimer 1.x compatibility and support policy #349.

Non-blocking checklist IDs

• V1-NB-01: Future fixed-team OpenMP worker ergonomics. Reuse Explore opt-in fixed-team OpenMP worker timing mode #294.
• V1-NB-02: Package-manager ownership versus readiness guidance. Tracked by Strategic question: decide package-manager ownership after v1.0 #355.
• V1-NB-03: Ubuntu 24.04 MPICH pFUnit runner migration. Reuse Track Ubuntu 24.04 MPICH pFUnit re-enable path #259.
• V1-NB-04: NVHPC serial smoke validation. Reuse Investigate NVHPC nvfortran serial smoke validation #256.
• V1-NB-05: Durable feature-mode benchmark artifacts. Keep non-blocking unless v1.0 release notes cite feature-mode benchmark trends.

Child issue task list

Release-blocking:

• Strategic question: define fTimer 1.x compatibility and support policy #349
• Feature: update v1.0 package version behavior and installed-consumer probes #350
• Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351
• Feature: refresh v1.0 release claims and evidence #352
• Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353
• Feature: prepare v1.0 release notes, validation record, and artifact closeout #354

Non-blocking / post-release:

• Strategic question: decide package-manager ownership after v1.0 #355
• Explore opt-in fixed-team OpenMP worker timing mode #294
• Track Ubuntu 24.04 MPICH pFUnit re-enable path #259
• Investigate NVHPC nvfortran serial smoke validation #256

Existing issues to reuse

• Explore opt-in fixed-team OpenMP worker timing mode #294 maps to V1-NB-01.
• Track Ubuntu 24.04 MPICH pFUnit re-enable path #259 maps to V1-NB-03 and cross-links V1-RB-06.
• Investigate NVHPC nvfortran serial smoke validation #256 maps to V1-NB-04.
• Umbrella: strategic release-readiness follow-ups from independent audit #302 through Spike OpenMP report and CSV helper extraction #316 are completed release-audit baseline work and should be cited rather than duplicated.

Release-blocking policy

This umbrella is labeled release-audit. Release-blocking status lives on the blocking child issues so individual decisions and PRs can close independently.

[jaharris87]

Orchestration status update:

First-wave delegated work is in progress in separate Codex worktrees:

• Strategic question: define fTimer 1.x compatibility and support policy #349: v1.0 / 1.x compatibility and support policy decision.
• Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353: MPICH MPI+OpenMP evidence-boundary decision.
• Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351: public API and user-facing output-surface classification, with an explicit alignment gate on Strategic question: define fTimer 1.x compatibility and support policy #349.

Dependent blockers are intentionally queued:

• Feature: update v1.0 package version behavior and installed-consumer probes #350 waits for Strategic question: define fTimer 1.x compatibility and support policy #349.
• Feature: refresh v1.0 release claims and evidence #352 waits for Strategic question: define fTimer 1.x compatibility and support policy #349, Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351, and Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353.
• Feature: prepare v1.0 release notes, validation record, and artifact closeout #354 remains last, after blocking decisions and release-facing updates are complete.

Reused issues #294, #259, and #256 remain non-blocking/post-release under their existing v1.0 disposition comments unless a maintainer explicitly changes scope.

[jaharris87]

Orchestration status update:

First-wave delegated work has completed as decision handoffs, not implementation PRs:

• Strategic question: define fTimer 1.x compatibility and support policy #349: compatibility/support policy options and recommendation posted on the issue. Paused on maintainer choice among SameMajorVersion, SameMinorVersion, or a hybrid source/package policy.
• Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351: public API/output-surface inventory and recommendation posted on the issue. Paused on maintainer choice to accept the current explicit surface for v1.0 or narrow it before release, aligned with Strategic question: define fTimer 1.x compatibility and support policy #349.
• Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353: MPICH MPI+OpenMP evidence-boundary options and recommendation posted on the issue. Paused on maintainer choice between local-evidence-backed caveated support and permanent CI release-validated coverage.

No PRs are currently merge-ready. Dependent issues remain queued:

• Feature: update v1.0 package version behavior and installed-consumer probes #350 waits for Strategic question: define fTimer 1.x compatibility and support policy #349.
• Feature: refresh v1.0 release claims and evidence #352 waits for Strategic question: define fTimer 1.x compatibility and support policy #349, Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351, and Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353.
• Feature: prepare v1.0 release notes, validation record, and artifact closeout #354 waits for all release-blocking decisions/updates.

The orchestrator will resume delegation once these maintainer decisions are recorded.

[jaharris87]

Maintainer decisions recorded for first-wave blockers:

• Strategic question: define fTimer 1.x compatibility and support policy #349: choose SameMajorVersion for 1.x package requests with explicit compiler/toolchain/MPI/OpenMP-mode .mod caveats.
• Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351: accept the current explicit public API/output surface for v1.0; keep CSV schemas stable by family/version, text reports human-facing but not parser-stable, and Explore opt-in fixed-team OpenMP worker timing mode #294 future/non-blocking.
• Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353: keep MPICH MPI+OpenMP hybrid local-evidence-backed/caveated for v1.0, not permanent CI-covered.

Next orchestration step: delegate #350 to implement package-version behavior and installed-consumer probes. #352 remains queued until #350 lands or is far enough along to avoid conflicting docs edits; #354 remains last.

[jaharris87]

#350 has been delegated to a fresh Codex worktree/thread for implementation of the decided v1.0 package-version policy.

Delegated scope:

• Apply Strategic question: define fTimer 1.x compatibility and support policy #349's SameMajorVersion decision for 1.x package requests.
• Update package-version probes and directly required package/install docs.
• Preserve Strategic question: freeze stable public API and user-facing output surfaces for 1.0 #351 public-surface and Strategic question: decide v1.0 MPICH MPI+OpenMP evidence boundary #353 evidence-boundary decisions.
• Open a ready-for-review PR and complete the repo review/CI workflow before handing back merge readiness.

Dependent #352 remains queued until #350 is ready or merged to avoid overlapping release-doc edits.