Description
Run the static engine release candidate review and prepare the final release packet.
This issue should gather all reports, classify remaining failures, decide whether they block release, and produce the artifact that justifies closing the static engine milestone.
The goal is to make the release decision evidence-based.
Requirements
-
Run full release CI gate.
-
Run conformance baseline.
-
Run compatibility corpus release subset.
-
Run snapshot determinism checks.
-
Run performance/guardrail reports.
-
Run architecture ownership review.
-
Run security/resilience audit.
-
Run docs consistency check.
-
Collect release candidate reports.
-
Classify failures:
-
release blocker;
-
accepted known failure;
-
deferred future milestone;
-
unsupported/out of scope;
-
flaky/non-blocking;
-
documentation-only fix required.
-
Link GitHub issues for blockers.
-
Add accepted failure rationale.
-
Add release risk summary.
-
Add final release packet document.
-
Include:
-
support matrix;
-
conformance summary;
-
compatibility summary;
-
performance summary;
-
guardrail summary;
-
known limitations;
-
open blocker list;
-
deferred milestone list;
-
release recommendation.
-
Do not close AW until blockers are resolved or explicitly accepted.
Exit Criteria
-
Release candidate review has been run.
-
Release packet exists.
-
Blockers are classified.
-
Accepted failures have rationale.
-
Deferred work points to future milestones.
-
Release recommendation is documented.
-
The issue is closeable when the release packet supports final closeout.
Description
Run the static engine release candidate review and prepare the final release packet.
This issue should gather all reports, classify remaining failures, decide whether they block release, and produce the artifact that justifies closing the static engine milestone.
The goal is to make the release decision evidence-based.
Requirements
Run full release CI gate.
Run conformance baseline.
Run compatibility corpus release subset.
Run snapshot determinism checks.
Run performance/guardrail reports.
Run architecture ownership review.
Run security/resilience audit.
Run docs consistency check.
Collect release candidate reports.
Classify failures:
release blocker;
accepted known failure;
deferred future milestone;
unsupported/out of scope;
flaky/non-blocking;
documentation-only fix required.
Link GitHub issues for blockers.
Add accepted failure rationale.
Add release risk summary.
Add final release packet document.
Include:
support matrix;
conformance summary;
compatibility summary;
performance summary;
guardrail summary;
known limitations;
open blocker list;
deferred milestone list;
release recommendation.
Do not close AW until blockers are resolved or explicitly accepted.
Exit Criteria
Release candidate review has been run.
Release packet exists.
Blockers are classified.
Accepted failures have rationale.
Deferred work points to future milestones.
Release recommendation is documented.
The issue is closeable when the release packet supports final closeout.