Skip to content

Add noetic-eol specific instructions to installation sections covering #760

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

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

urfeex
Copy link
Member

@urfeex urfeex commented Jul 29, 2025

  • ROS 1 is EOL
  • Updates on how to build from source (rosdep)
  • Reference to ROS-O

@v4hn Is "ROS-O" or "ROS One" the preferred term to use?

- ROS 1 is EOL
- Updates on how to build from source (rosdep)
- Reference to ROS-O
@urfeex urfeex requested a review from a team July 29, 2025 09:24
@urfeex urfeex added the documentation Indicates that improvements or additions to documentation are needed label Jul 29, 2025
@v4hn
Copy link
Contributor

v4hn commented Jul 29, 2025

Is "ROS-O" or "ROS One" the preferred term to use?

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!

@urfeex
Copy link
Member Author

urfeex commented Jul 29, 2025

Thank you for the input! I've updated the two paragraphs accordingly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Indicates that improvements or additions to documentation are needed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants