Skip to content

tracker(weld): move EEST to EELS ⚙️🧪⚒️🔥 #1839

@danceratopz

Description

@danceratopz

Tracking issue for EEST related tasks necessary for "The Weld": Moving ./src and ./tests/ from execution-spec-tests to execution-specs.

All issues can/must be completed Pre-Switch, unless otherwise stated.

Future Workflow Conventions

Repo Alignment

EEST Packaging in ethereum-execution

Tooling (ruff, mypy, codespell, tox)

Ruff: Line Length

Ruff: Rule Alignment

Mypy

  • Enforce stricter mypy rules on EEST? Or straight-up switch to ty?

pytest/framework tests

  • enable running tox -e pytest in execution-specs.

Tox

WIP

Docs

  • What do we put at eest.ethereum.org? Redirect to execution-specs mkdocs website?
  • Merging docc and mkdocs concept.
  • mkdocs versioning concept; instead of per-release, we simply version by major fork branch (from prague on), e.g, forks/prague, forks/osaka, forks/amsterdam.

Other Sub-Tasks

Sub-issues

Metadata

Metadata

Assignees

No one assigned

    Labels

    P-hightrackerTracking issue for projects with sub-tasks

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions