Next release checklist
Open
- Dominant language
- Python
- Stars
- 63
- Forks
- 13
- PR merge metrics
- No merged PRs in 30d
Description
- [x] https://github.com/crytic/tealer/issues/1
- [x] https://github.com/crytic/tealer/issues/2
In addition, we should prepare the next release to be ready for `pip` to ease the installation
Contributor guide
Research direction
Review completed issues #1 and #2, then inspect how this Python project is currently packaged and installed. Determine the release steps needed to make the next version installable through pip; done means those steps are documented or implemented and a fresh pip installation works.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- build-system, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100