Open
Conversation
This is useful for first time contributors and contributors who may not be able to attend PMC meetings as its hard to keep track of what our latest policies are. Signed-off-by: Arjo Chakravarty <arjoc@intrinsic.ai>
azeey
reviewed
Jan 28, 2026
| - If you have a new API/ABI Breaking change or are changing the bevaviour of a system | ||
| please target the main branch. | ||
| - If you are making interdependent changes to multiple repositories without breaking API or ABI, it is recommended to base your new branches off of the branch used in the upcoming collection to simplify automated testing of the changes and the review process. For example, at the time this documentation is being written the upcoming Jetty collection branches are documented in [gazebodistro](). Your changes may be backported to an existing release once all the changes have been merged. | ||
| - If your changes don't break API/ABI and you would like them to be released to an existing release with major version N, then use branch gz-<library>N as the base. |
Contributor
There was a problem hiding this comment.
I think we should encourage the default branch in this case and backport. Once we get gazebo-tooling/release-tools#1403 closed, main will be the default branch.
| You may also want to check which base branch you wish to commit to: | ||
| - If you have a new API/ABI Breaking change or are changing the bevaviour of a system | ||
| please target the main branch. | ||
| - If you are making interdependent changes to multiple repositories without breaking API or ABI, it is recommended to base your new branches off of the branch used in the upcoming collection to simplify automated testing of the changes and the review process. For example, at the time this documentation is being written the upcoming Jetty collection branches are documented in [gazebodistro](). Your changes may be backported to an existing release once all the changes have been merged. |
Contributor
There was a problem hiding this comment.
A lot of this is covered in https://gazebosim.org/docs/latest/contributing/. Should we just point to that instead and update that as necessary?
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.
🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸🔸
🎉 New feature
Closes #
Summary
This is useful for first time contributors and contributors who may not be able to attend PMC meetings as its hard to keep track of what our latest policies are.
Test it
Checklist
codecheckpassed (See contributing)Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining
Signed-off-bymessages.