Skip to content

meta(1.0): tracking issue for 1.0 milestone #8574

@zerosnacks

Description

@zerosnacks

Tracking issue for 1.0 milestone

Ticket to be used for discussion and track high-level progress.

Link to trackers:

To discuss:

Tip:

Use the issue tracker to more easily view / edit the milestone: https://github.com/foundry-rs/foundry/issues?q=is%3Aopen+is%3Aissue+milestone%3Av1.0.0


Preparation:

  • Identify all active tickets
  • Label all tickets + PRs
  • Apply a high-level filter to milestone tickets, make sure all tickets in milestone are actionable
  • Determine blockers / ticket dependency tree
  • Label all tickets with a priority according to bug severity / feature impact / complexity matrix
  • Determine status of current open PRs

Abstract scope 1.0:

  • Focus on stability, correctness and completeness:
    • Testing (unit, fuzz, invariant)
    • Contract deployment
    • Contract verification
    • Gas measurement / reporting
    • Test coverage
  • Compatibility with EVM / Ethereum L2s (precompiles)
  • Priority: forge > anvil + cast + debugger> chisel
  • Correct behavior of --json flag and correct rendering to stdout / stderr

Breaking changes ( T-likely-breaking Type: requires changes that can be breaking ) - to be done before 1.0 release, with the possibility to opt out:


Out of scope for 1.0, better suited after:


Before release:


Before publishing:

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    Status

    Next Up

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions