Skip to content

1.2.0rc1

1.2.0rc1 is the first release candidate for the 1.2 workflow/orchestration release.

Scope freeze

The scientific estimator surface is unchanged from qualified 1.1 plus the already-qualified 1.2 workflow layer. This RC adds no estimator, numerical method, dependency, hidden analytical default, root-namespace promotion, or workflow-contract expansion.

The 1.2 feature surface is the completed W1–W4 programme:

  • typed workflow infrastructure with explicit decision and step provenance;
  • sparse FPCA, paired/asynchronous sparse MFPCA, sparse multilevel and sparse prediction workflows;
  • dense FPCA, function-on-scalar, functional mixed-effects and generalized functional workflows;
  • explicit recurrence/RQA orchestration;
  • canonical workflow plotting composition;
  • portable workflow bundles, reporting/tables and installed-wheel product qualification; and
  • a frozen module-scoped workflow API audit under eyetrajectoriespy.workflows.

Qualification basis

Pre-RC protected main 11cefc4f81957ab5e3033ba18b993e49ffb01c3d passed 29/29 workflow groups with zero failures after PR #219.

The retained installed-wheel W4 artifact:

  • executes all 10 workflow contracts from installed 1.2.0.dev0;
  • records zero release-blocking friction;
  • uses no repository-private helpers;
  • retains no workflow warnings; and
  • verifies representative FPCA, sparse-MFPCA and recurrence workflow-bundle checksums.

WORKFLOW_API_AUDIT.json freezes 49 module-scoped workflow exports, 10 workflow entry points and 10 unique versioned contracts with root promotion disabled.

RC qualification contract

Literal RC qualification must now:

  1. align source, citation, workflow-manifest and qualification-ledger identity to 1.2.0rc1;
  2. generate fresh exact-RC package-wide performance evidence rather than relabel 1.1.0 measurements;
  3. pass the complete pull-request matrix on one exact RC head;
  4. merge through protected main;
  5. pass the complete exact-main matrix again; and
  6. keep GitHub/PyPI publication readiness jointly false throughout qualification.

Only after those gates pass may a separate governance-only change arm publication.

Publication state

This RC qualification does not publish anything. Stable/default production remains 1.1.0 until an explicit later publication succeeds.