nebari-dev / nebari-dev/nebari-docs
Update release documentation to reflect changes in branching strategy
Open
@marcelovilla is already working on this.
Since Apr 23, 2024.
area: community 🪴
- Dominant language
- No language data
- Stars
- 21
- Forks
- 40
- Avg merge
- 19h 50m
- Merged PRs (30d)
- 6
Description
Context
We are in the process of deprecating the main branch, keeping only develop. We need to update the release documentation to reflect this changes and guide contributors when preparing a new release
Value and/or benefit
We'll have consistent documentation, allowing any interested person to easily understand how to contribute to the release process.
Anything else?
No response
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.
Assessment
This issue has not been assessed yet.