Skip to content

Use a single file for migration + release notes #1611

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

Merged
merged 1 commit into from
Jul 14, 2024

Conversation

christophfroehlich
Copy link
Contributor

@christophfroehlich christophfroehlich commented Jul 13, 2024

we decided to show only the notes for the respective version in the docs, instead of all incremental distro upgrades

this makes backports easier and should avoid merge conflicts in the docs.

needs ros-controls/control.ros.org#324

Copy link
Member

@saikishor saikishor left a comment

Choose a reason for hiding this comment

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

Sounds good to me to have one release_notes per branch. As you said, it is better for backporting and all!

@christophfroehlich christophfroehlich merged commit 0c17054 into master Jul 14, 2024
4 of 6 checks passed
@christophfroehlich christophfroehlich deleted the cleanup_notes branch July 14, 2024 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants