OpenZeppelin / OpenZeppelin/compact-contracts
Audit and cut 0.2.0 stable release
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 55
- Forks
- 29
- Avg merge
- 5d 7h
- Merged PRs (30d)
- 25
Description
🧐 Motivation
Per the release-train model, each ~3-week alpha is a normal (unaudited) feature release. Auditing that alpha and fixing its findings produces the clean, no-suffix stable release (no suffix = audited). This issue tracks the audit that promotes 0.2.0-alpha to the audited 0.2.0 stable release.
Release train board: https://github.com/orgs/OpenZeppelin/projects/109
📝 Details
Scope: the feature surface frozen in the 0.2.0-alpha release candidate (frozen RC commit handed to the security services team).
Checklist:
- Freeze
0.2.0-alphaRC commit and share with security services - Audit duration estimated
- Audit completed
- Findings triaged
- Fixes merged
-
0.2.0stable cut (audited)
Timeline: TBD.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the release-train board and the frozen 0.2.0-alpha release-candidate commit described in the issue; no files, tests, or entry points are named. The work is done when the audit is completed, findings are triaged, fixes are merged, and the audited 0.2.0 stable release is cut.
Written by the indexing model from the issue text.
Assessment
- Domain
- release, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100