Explore a branching strategy
Nobody has claimed this yet.
- Dominant language
- Markdown
- Stars
- 46
- Forks
- 40
- Avg merge
- 4h 3m
- Merged PRs (30d)
- 6
Description
To avoid bumping versions often, we should explore a branching strategy that lets us iterate without releasing, possibly using helm-git to iterate on something so that version bumps are (1) rarer and (2) more meaningful
Alternatively, we can scratch this and merge everything to main / bump versions often 😄
Related to #34 because artifcathub tracks changes "per release," IIUC.
It could also be beneficial to have "release candidate" branches or a dev branch, for instance, because that gives a bit of protection for new contributors to have their changes more thoroughly vetted before a release is deployed.
- Evaluate options for branching and build/release strategies, along with
helm-gitand what the dev / testing workflow might look like - Learn more about #34 / artifacthub changelog
- Weigh pros / cons, and decide on future direction
- Document our decision in
CONTRIBUTING.md
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 reviewing issue #34 and ArtifactHub's changelog behavior, then evaluate the listed branching, release-candidate, dev-branch, and helm-git options. Compare their pros and cons and document the chosen future direction and workflow in CONTRIBUTING.md.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, helm
- Domain
- build-system, documentation, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100