Jetty changelog

[caguero]

Part of #18.

Update changelog for gz-tools 2.1.0, with an estimated release date just a little before the community meeting.

Test it

Compare to gz-tools2_2.0.2...main

Summary

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
• Was GenAI used to generate this PR? If so, make sure to add "Generated-by" to your commits. (See this policy for more info.)

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

[azeey]

I don't believe we are releasing gz-tools3. cc @scpeters

[caguero]

I don't believe we are releasing gz-tools3. cc @scpeters

CMakelists.txt is at version 3.0.0. I can restore it to 2.x.x. Should I?

[azeey]

No, we're using the gz-tools2 branch, so no need to change anything on main. https://github.com/gazebo-tooling/gazebodistro/blob/33088b8e5fb2df8c4c4276c0fd9cf30a0530ca81/collection-jetty.yaml#L54

[caguero]

No, we're using the gz-tools2 branch, so no need to change anything on main. https://github.com/gazebo-tooling/gazebodistro/blob/33088b8e5fb2df8c4c4276c0fd9cf30a0530ca81/collection-jetty.yaml#L54

Changelog updated. Should we backport this patch to gz-tools2 after merge, then?

[azeey]

Changelog updated. Should we backport this patch to gz-tools2 after merge, then?

I guess? I would typically just create this PR on gz-tools2 branch.

[scpeters]

the changelog content includes commits from the main branch; we should probably start over from the gz-tools2 branch

[caguero]

Let's redo it targetting gz-tools2.