Skip to content

S8: Release 2.0.0 — to_dataframe and the dataframe extra removed #72

Description

@Polichinel

Epic: #66 · Wave 4 · Blocked by: S7 (#63) · MAJOR bump under ADR-022 §5

The work

As S6, with: pyproject.toml:32.0.0; ## [2.0.0] — YYYY-MM-DD with ### Removed and the migration; ADR-022 §7 checklist — rule 2: yes, to_dataframe removed, the DeprecationWarning shipped in 1.1.0 (cite the section); previously-accepted input fails: yes, to_dataframe callers and [dataframe] installers, migration stated, consumers notified before the tag (views-reporting must widen <2.0.0 before they can resolve — S9; vpc's tripwire is their cue — S10); version bump matches the change class; MetricFrame format unchanged. Register dated block. The 2.0.0 section must not reuse the 0.5.0 table header or "For the … rows" phrasing. Tag, publish (gated), back-merge.

Acceptance criteria

  • CHANGELOG-section guard red before, green after
  • Publish workflow green including tests; PyPI shows 2.0.0
  • main back-merged; register updated
  • views-reporting and vpc notified before the tag, with S9/S10 linked

Validation

grep -n '^version' pyproject.toml; grep -n '^## \[2.0.0\] — ' CHANGELOG.md
conda run --name views_pipeline pytest tests/ -q; bash documentation/validate_docs.sh
gh release view v2.0.0 --json isDraft,publishedAt

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    implementationCode changerisk-registerOpens, closes or reconciles entries in reports/technical_risk_register.mdstoryA single, independently implementable and reviewable unit of an epic

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions