Repository navigation
docs(stable14): align maintainer instructions with release branches - #139
Merged
Merged
Conversation
Signed-off-by: Vitor Mattos <1079143+vitormattos@users.noreply.github.com>
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.
Scope
Align the two maintainer-oriented Markdown files in the
stable14documentation branch with the branch-per-LibreSign-version architecture implemented in #130.README.md: replace the removedversioned/baseand inheritance instructions with editing the complete manual on the targetstableNNbranch.docs/maintainers/versioning.md: document backports, source SHA pinning, current CI, preview, and correct release workflow.The branch has a protected pull-request + code-owner review requirement; this PR follows that policy instead of pushing directly to
stable14.Dependency: review and merge #130 before merging this guidance update. The commit is cryptographically signed with DCO. No merge is authorized here.