-
Notifications
You must be signed in to change notification settings - Fork 668
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
New release after #406 #412
Comments
Hi @ahornung Can we please get the following PRs merged first (both minor and CI/ROS-release related): The diff between the last release (1.9.8) and master is the following: v1.9.8...devel - we may need to bump the minor version rather than a patch version? What do you think? |
We also need this to be released in order to make octomap build on Noble; see https://build.ros2.org/job/Rbin_uN64__octomap__ubuntu_noble_amd64__binary/8/console . In particular, we need #373 released so it will build cleanly. It would also be nice to get #415 in, though it isn't strictly required to make it build (it will just have warnings). |
Thanks! I'll have a look asap. Traveling right now, so it will be in a few days.
|
@wxmerkt @clalancette thanks, looking good so far with the PRs! Updated release coming soon. |
Thank you, much appreciated! |
Done, v1.10.0 released! |
Fantastic, thank you so much. Are you planning on doing a bloom-release of this for ROS 2, or would you prefer that I do it? |
I'm not really tracking or maintaining the ROS releases anymore, so if either @wxmerkt or you do it that's fine by me. |
All right, I'll go ahead and do it. |
And here is the release into Rolling: ros/rosdistro#40273 |
Thank you for the time to review, merge, and release @ahornung - much appreciated. @clalancette Thanks for making the release. I had some issues with bloom-release creating the release but not opening the PR |
Thank you all, much appreciated! |
Hi there!
Any chance there could be a new patch version after #406? This is a great fix and would be great to have a tagged version for this.
Thank you!
The text was updated successfully, but these errors were encountered: