Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update contributing policy #525

Merged
merged 3 commits into from
Oct 22, 2024
Merged

Update contributing policy #525

merged 3 commits into from
Oct 22, 2024

Conversation

iche033
Copy link
Contributor

@iche033 iche033 commented Oct 14, 2024

🦟 Bug fix

Summary

Updated to reflect the new policy introduced in https://community.gazebosim.org/t/gazebo-policy-update-new-backporting-policy/2880.

  • updated to say contributions should now target latest release
  • moved instructions for backporting PR up earlier in the section.

Checklist

  • Signed all commits for DCO
  • Added tests
  • Updated documentation (as needed)
  • Updated migration guide (as needed)
  • Consider updating Python bindings (if the library has them)
  • codecheck passed (See contributing)
  • All tests passed (See test coverage)
  • While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Copy link
Contributor

@peci1 peci1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, LGTM with one comment in code.

contributing.md Outdated
# Fix conflicts
git commit -sam"Backport from N to M"
# Open pull request
# Do not squash, rebase instead
* Periodically, a maintainer will **forward-port** changes to newer release
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about here? Isn't it now bidirectional, or mostly back-port way?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eventually, I think it will be mostly back-ports, but right now we have a mix of both. But I agree this sentence could be updated to indicate back-ports are now more likely.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

updated sentence so that forward port does not sound like a periodic thing we do 4724943

contributing.md Show resolved Hide resolved
contributing.md Outdated
# Fix conflicts
git commit -sam"Backport from N to M"
# Open pull request
# Do not squash, rebase instead
* Periodically, a maintainer will **forward-port** changes to newer release
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Eventually, I think it will be mostly back-ports, but right now we have a mix of both. But I agree this sentence could be updated to indicate back-ports are now more likely.

@azeey azeey merged commit 0e243eb into master Oct 22, 2024
5 checks passed
@azeey azeey deleted the contributing_updates branch October 22, 2024 14:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

3 participants