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

Sync melodic changes to noetic #79

Open
2 of 4 tasks
JeroenDM opened this issue Nov 7, 2021 · 4 comments
Open
2 of 4 tasks

Sync melodic changes to noetic #79

JeroenDM opened this issue Nov 7, 2021 · 4 comments

Comments

@JeroenDM
Copy link
Owner

JeroenDM commented Nov 7, 2021

edit now the question is whether to sync melodic to noetic or noetic to melodic to unify the branches. I think melodic to noetic will be the easiest.

@simonschmeisser
Copy link
Collaborator

Generally once opw gets released for melodic we should not need a different branch for melodic and noetic any longer, right?

@JeroenDM
Copy link
Owner Author

JeroenDM commented Nov 8, 2021

Ah, indeed. It was kinetic vs melodic that involved api changes in MoveIt. If they both rely on the same released version of opw they should be fine I think.

(Mentioning kinetic make me feel old :) and it is not even the first version of ROS I started using.)

So we could simply sync melodic with noetic in either of the branches and move one of them over to MoveIt.

@JeroenDM
Copy link
Owner Author

To continue the thread from #77.

This also seems to suggest releasing the IK plugin should be possible now @JeroenDM.

Do you mean releasing a new version?

I assume you mean releasing a new version for melodic that uses the recently released opw-kinematics for melodic. I'll update this issue and will carve out some time next week to clean this up before moving it into MoveIt.

@JeroenDM
Copy link
Owner Author

Started in #82

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

No branches or pull requests

2 participants