rhobs / rhobs/observability-operator
Rethink versioning and release workflow
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 51
- Forks
- 90
- Avg merge
- 5d 15h
- Merged PRs (30d)
- 22
Description
The changelog specifies we use standard-version for version releases. This however seems deprecated. Should we rethink this decision?
Contributor guide
No contributing guide indexed for this repository
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 changelog and its standard-version release instructions. Investigate whether the documented workflow is still appropriate and determine what release process should replace or revise it. Done means the project has a decided release approach and its documentation reflects that decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100