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

Add missing floating joint components #266

Merged
merged 2 commits into from
Jan 19, 2025

Conversation

Levi-Armstrong
Copy link
Contributor

No description provided.

@Levi-Armstrong Levi-Armstrong force-pushed the feature/add-missing-floating-joint-components branch from 46d28ff to 492413c Compare January 19, 2025 02:36
@Levi-Armstrong
Copy link
Contributor Author

@rjoomen Would you have time to port these to tesseract_ros2?

@Levi-Armstrong Levi-Armstrong merged commit d12239b into master Jan 19, 2025
3 of 4 checks passed
@Levi-Armstrong Levi-Armstrong deleted the feature/add-missing-floating-joint-components branch January 19, 2025 05:02
@rjoomen
Copy link
Contributor

rjoomen commented Jan 19, 2025

@rjoomen Would you have time to port these to tesseract_ros2?

Sure, I'll do that sometime this week.

How exactly do I create a release, though? catkin_generate_changelog and catkin_prepare_release, I suppose, and then?

@Levi-Armstrong
Copy link
Contributor Author

Release process I follow:

  • catkin_generate_changelog
  • commit changes but do not push
  • catkin_prepare_release (only patch increment is needed here)
  • then in GitHub I go to the release page and create a new release from the newly create tag.
  • On the other repos I would then copy the debian artifacts created from tag debian CI to the release but that is not needed here.

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