docs: update CONTRIBUTING with v2 branching strategy#1804
Merged
Conversation
Clarify that main is now the v2 development branch where breaking changes are welcome, and v1.x is the maintenance branch for security and critical bug fixes only.
felixweinberger
approved these changes
Dec 19, 2025
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
2 participants
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.
Clarify the branching strategy now that v2 development has begun.
Motivation and Context
With the v2 branching strategy in place (
mainfor v2 development,v1.xfor maintenance), the CONTRIBUTING guide needed updating to help contributors target the correct branch.How Has This Been Tested?
Documentation change only.
Breaking Changes
None.
Types of changes
Checklist