Ionic Changelog

[scpeters]

🎉 New feature

Part of gazebo-tooling/release-tools#1092

Summary

Update changelog for gz-physics 8.0.0, with an unspecified release date.

Test it

Compare to gz-physics7_7.3.0...main

Note: I excluded the following Harmonic PRs that have not been released as of 7.3.0 since they will be released in Harmonic. Please advise if I should add them.

• bullet-featherstone: Enforce joint velocity and effort limits for velocity control commands #658
• Fix CTAD compile warnings #663
• bullet-featherstone: Support empty links #665

Checklist

• Signed all commits for DCO
• Added tests
• Added example and/or tutorial
• 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.

[azeey]

I think we should include them. It'll make it easier to create the Gazebo Ionic release notes that includes all development that happened this year, not just the ones that went into the main branches. One way I'm thinking of it is if we did all our new development on the main branches, but backported to older versions, we would include these changes in the main Changelog right?

[scpeters]

I think we should include them. It'll make it easier to create the Gazebo Ionic release notes that includes all development that happened this year, not just the ones that went into the main branches. One way I'm thinking of it is if we did all our new development on the main branches, but backported to older versions, we would include these changes in the main Changelog right?

it depends on what we want the Changelog to represent:

• should it represent the work we've done in the past year? in which case we should include all development done since the Harmonic release regardless of branch
• OR should it represent the features only available on Ionic so people know what they are missing if they don't upgrade. In which case we wouldn't include features that were backported

I've been constructing changelogs based on the second approach but am willing to revise them if we agree that the first approach is preferred

[azeey]

Okay, per our discussion in the weekly meeting, the Changelog for a major release should represent changes from the last release of the stable version. This version should also be explicitly stated at the beginning of the Changelog.

[scpeters]

Okay, per our discussion in the weekly meeting, the Changelog for a major release should represent changes from the last release of the stable version. This version should also be explicitly stated at the beginning of the Changelog.

I've updated our changelog script in gazebo-tooling/release-tools#1175 to print the baseline

[scpeters]

I've updated the changelog to add a baseline and some missing entries and also set the VERSION_SUFFIX to pre1 so we can make the prerelease without another pull request