Workflow for merging bug fixes
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 2.6k
- Forks
- 779
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 27
Description
As discussed on the last call, we'd like to be better about semantic versioning. The plan for this is to cut release branches which we can back port bug fixes onto, and keep new features for minor releases. We need to develop some processes for marking which PRs should get back ported, and for doing the back porting.
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
No files, tests, or entry points are named. Start by turning the semantic-versioning plan into an agreed process for marking PRs for backporting, maintaining release branches, and keeping new features for minor releases; done means the workflow is documented and actionable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100