Goal
The 2.0 release checklist: benchmark acceptance, final gates, tag and publish.
Why
The release plan set a hard acceptance bar — no metric slower than 1.x, and the flip
(bridge removal + parquet) is expected to win on load and summary; if it doesn't, that
is a signal to investigate before shipping, not after.
Plan: architecture-plan/cellpy2-release-and-branching-plan.md §4 and §6;
architecture plan §6 row 3.6.
Gates
Then
Goal
The 2.0 release checklist: benchmark acceptance, final gates, tag and publish.
Why
The release plan set a hard acceptance bar — no metric slower than 1.x, and the flip
(bridge removal + parquet) is expected to win on load and summary; if it doesn't, that
is a signal to investigate before shipping, not after.
Plan:
architecture-plan/cellpy2-release-and-branching-plan.md§4 and §6;architecture plan §6 row 3.6.
Gates
show the expected bridge-removal win (tiered gate per golden test fails #476).
and named (no silently widened tolerances).
essential (linux / uv)andfull (linux / uv).DEPRECATIONS.mdcomplete; migration guide published.cellpycorepinned to an exact released version.Then
v2.0.0, publish to PyPI, update the conda feedstock.v1.xbranch state and start the 12-month bugfix-only window(decision Stage 0.11: Decision register — the calls that gate Stage 1+ #438-6) from this date.