Add noetic-eol specific instructions to installation sections covering#760
Merged
Merged
Conversation
- ROS 1 is EOL - Updates on how to build from source (rosdep) - Reference to ROS-O
urfeex
added
the
documentation
Contributor
There is no clear preference, but ROS-O is shorter. Maybe it makes sense to clarify what you mean by "binary release", because https://ros.packages.techfak.net/ clearly is a binary release, just not noetic. Thanks for mentioning it! |
Member
Author
|
Thank you for the input! I've updated the two paragraphs accordingly. |
URJala
requested changes
Sep 16, 2025
Co-authored-by: URJala <159417921+URJala@users.noreply.github.com>
URJala
approved these changes
Sep 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
@v4hn Is "ROS-O" or "ROS One" the preferred term to use?