Make master the canonical development branch - #100
Merged
Conversation
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
1 participant
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.
Closes #53 after merge.
Policy
masteris the sole long-lived canonical development branch.master.master.devis retired/deprecated and receives no new work.Checked-in changes
docs/development.orgwith the permanent branch invariant and merge/test policy;devfrom normal Smoke and Container Stack push/PR filters;masterand remove itsdevpush filter;masterPRs as part of Retire dev: final reconciliation into master #99 because otherwise the reconciliation could not run that gate.The special schema-lock
agent/**push trigger remains as a direct branch test hook; it is not an integration target. Normal PRs still target master.Historical PR disposition
#95 remains valid and will be retargeted/refreshed onto master after this policy PR lands. #79 remains a separate AGPL legal/contributor-permission review and is not folded into runtime work.