Repository navigation
docs: describe the maintenance and next-minor develop lines - #350
Merged
Merged
Conversation
main now has two develop lines, develop/0.5.1 and develop/0.6.0, replacing develop/0.5.0. Rewrite the branch model, the flow of fixes between the lines, the promotion path and the steps after a stable release. Record the website conflict and the Homebrew tap audit found while releasing v0.5.0, and drop the stale macOS port caveats.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Replaces the single
develop/0.5.0line inCONTRIBUTING.md, the runbook andcicd.mdwithdevelop/0.5.1anddevelop/0.6.0.Targets
mainbecause contributors readCONTRIBUTING.mdthere, and it should not name a deleted branch until v0.5.1. Docs only, so it does not touchversion.jsonor fire the website sync. Mergemainforward into both develop lines afterwards.