-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Please release for Eloquent #561
Comments
@SteveMacenski |
I am also curious about release for ROS2 Eloquent. |
Well, they created a branch for Eloquent: eloquent-devel. You can simply install it from source while they release it as a Debian package. |
@ROBOTIS-Will following up - did you guys manage a release yet? |
@andrestoga @SteveMacenski Hi, I've created a branch for the eloquent so that I don't forget to release it. A massive binary package updates is scheduled in May along with our eManual instructions. Sorry for the delay! |
I'm afraid that I have to announce a bad news for the Eloquent developers. We have decided to skip the Eloquent and focus on the Foxy as Eloquent is marked for EOL on this November. We're expecting to be able to deliver TurtleBot3 Foxy contents partially from August. Thank you. |
Whats the blocker? You should just need to run bloom? |
@ROBOTIS-Will maybe we should get on a call and chat. If we can't expect reliable support for the TB3 product line, we may decide to drop support for it on navigation2. |
@SteveMacenski |
I appreciate that, thank you. It may still be worthwhile to get on a call at some point in the next week or so so that I can get an appreciation for your position on the TB3 repos. I noticed this week that the ros2 branches of this haven't moved in several months and it makes me a bit nervous given how tightly coupled it is with Nav2. |
@ROBOTIS-Will are you guys still releasing for Eloquent? |
@andrestoga |
There is no existing release for eloquent and there are customers asking for it in navigation2: ros-navigation/navigation2#1618
The text was updated successfully, but these errors were encountered: