spin release infrastructure out to a separate project
Open
Nobody has claimed this yet.
release-infrastructure
- Dominant language
- Python
- Stars
- 838
- Forks
- 123
- Avg merge
- 7h 58m
- Merged PRs (30d)
- 12
Description
Our little home-grown release.py doesn't really work properly (has it ever?) and should not be bespoke to Klein. It should have its own project, with tests.
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 by examining release.py to understand the existing release infrastructure and its current behavior. Define the separate project's scope and add tests for it; done means the release tooling is no longer bespoke to Klein and the new project has test coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100