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

Request to release 1.0.0 on all ROS2 distros #22

Open
saikishor opened this issue Aug 14, 2024 · 7 comments
Open

Request to release 1.0.0 on all ROS2 distros #22

saikishor opened this issue Aug 14, 2024 · 7 comments

Comments

@saikishor
Copy link
Contributor

Hello!

Thanks for such a great work. I'm writing here to know if it is possible to release the 1.0.0 on Humble, Jazzy and Rolling ROS 2 distros.

Thank you!

@facontidavide
Copy link
Collaborator

U should, shouldn't I?

@saikishor
Copy link
Contributor Author

U should, shouldn't I?

Sorry, I didn't get what you mean 😅😅
I could build them locally yes, it would be great if they are available as binaries. I'm thinking of a possible integration into the ROS2 control framework. So, the integration would be easier.

Thank you?

@facontidavide
Copy link
Collaborator

I am not sure if I am ready for the 1.0 version. But, at the same time, I have no time to devote to this library, for the time being

@saikishor
Copy link
Contributor Author

I am not sure if I am ready for the 1.0 version. But, at the same time, I have no time to devote to this library, for the time being

Gotcha. I saw the tag 1.0.0 and I thought it was already ready. Sorry for my misunderstanding. In that case, can 0.9.4 be released for Humble?

@facontidavide
Copy link
Collaborator

Let me see if I can first address #19

@saikishor
Copy link
Contributor Author

Sure. Thank you @facontidavide 🙏🏽🙏🏽

@henrygerardmoore
Copy link
Collaborator

henrygerardmoore commented Nov 4, 2024

@facontidavide Can we create a new ROS release? It would be nice to first address #19 and #34, perhaps, but I think there have been some improvements since the last ROS release that are worth capturing before those are complete. And doing this would also close #33, I think.

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

3 participants