Updating Rolling docs to Ubuntu Noble. (ros2#4240)

* Updating Rolling docs to Ubuntu Noble. Signed-off-by: Marco A. Gutierrez <[email protected]> Co-authored-by: Chris Lalancette <[email protected]>
CursedRock17 · Apr 16, 2024 · 3f6ddb9 · 3f6ddb9
1 parent fdec5e2
commit 3f6ddb9
Show file tree

Hide file tree

Showing 12 changed files with 18 additions and 43 deletions.
diff --git a/README.md b/README.md
@@ -29,7 +29,7 @@ pip install -r requirements.txt -c constraints.txt
 
 ### Pinned versions
 
-For development we currently use Jammy as our build platform.
+For development we currently use Noble as our build platform.
 And all python versions are pinned in the constraints file to make sure that things are reproducible.
 To upgrade the system validate that things are working and then use `pip freeze > constraints.txt` to lock in the versions to upgrade.
 

diff --git a/source/How-To-Guides/Using-Custom-Rosdistro.rst b/source/How-To-Guides/Using-Custom-Rosdistro.rst
@@ -18,7 +18,7 @@ However, there are occasions where a user would like the assert further control
 This guide walks through how to set a version of rosdistro to use on your system.
 
 The motivating example that this guide will use is a desire to use a previous version of Rolling due to a breakage on your development computer or Continuous Integration.
-It is possible that during transition periods from one operating system to another, Rolling on the older operating system may become unusable due to support shifting to a new OS (i.e. moving to Ubuntu 22.04 to 24.04).
+It is possible that during transition periods from one operating system to another, Rolling on the older operating system may become unusable due to support shifting to a new OS (i.e. moving from Ubuntu 22.04 to 24.04).
 Thus, we wish to set a prior version of rosdistro that aligns with a working Rolling distribution on a given operating system to keep our systems functioning before upgrading to the new operating system.
 
 Important Preliminaries

diff --git a/source/Installation.rst b/source/Installation.rst
@@ -27,7 +27,7 @@ If you are not running any of the following operating systems you may need to bu
 
 We provide ROS 2 binary packages for the following platforms:
 
-* Ubuntu Linux - Jammy Jellyfish (22.04)
+* Ubuntu Linux - Noble Numbat (24.04)
 
   * :doc:`Debian packages <Installation/Ubuntu-Install-Debians>` (recommended)
   * :doc:`"fat" archive <Installation/Alternatives/Ubuntu-Install-Binary>`

diff --git a/source/Installation/Alternatives/Ubuntu-Development-Setup.rst b/source/Installation/Alternatives/Ubuntu-Development-Setup.rst
@@ -15,7 +15,7 @@ System requirements
 -------------------
 The current Debian-based target platforms for {DISTRO_TITLE_FULL} are:
 
-- Tier 1: Ubuntu Linux - Jammy (22.04) 64-bit
+- Tier 1: Ubuntu Linux - Noble (24.04) 64-bit
 - Tier 3: Debian Linux - Bullseye (11) 64-bit
 
 As defined in `REP 2000 <https://www.ros.org/reps/rep-2000.html>`_.
@@ -146,12 +146,6 @@ Next steps
 
 Continue with the :doc:`tutorials and demos <../../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
 
-Use the ROS 1 bridge (optional)
--------------------------------
-
-The ROS 1 bridge can connect topics from ROS 1 to ROS 2 and vice-versa.
-See the dedicated :doc:`document <../../How-To-Guides/Using-ros1_bridge-Jammy-upstream>` on how to build and use the ROS 1 bridge.
-
 Alternate compilers
 -------------------
 

diff --git a/source/Installation/Alternatives/Ubuntu-Install-Binary.rst b/source/Installation/Alternatives/Ubuntu-Install-Binary.rst
@@ -22,7 +22,7 @@ There are also :doc:`Debian packages <../Ubuntu-Install-Debians>` available.
 System requirements
 -------------------
 
-We currently support Ubuntu Linux Jammy (22.04) 64-bit x86 and 64-bit ARM.
+We currently support Ubuntu Noble (24.04) 64-bit x86 and 64-bit ARM.
 The Rolling Ridley distribution will change target platforms from time to time as new platforms are selected for development.
 Most people will want to use a stable ROS distribution.
 
@@ -136,12 +136,6 @@ Next steps
 
 Continue with the :doc:`tutorials and demos <../../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
 
-Use the ROS 1 bridge (optional)
--------------------------------
-
-The ROS 1 bridge can connect topics from ROS 1 to ROS 2 and vice-versa.
-See the dedicated :doc:`document <../../How-To-Guides/Using-ros1_bridge-Jammy-upstream>` on how to build and use the ROS 1 bridge.
-
 Troubleshoot
 ------------
 

diff --git a/source/Installation/Testing.rst b/source/Installation/Testing.rst
@@ -24,12 +24,12 @@ For Debian-based operating systems, you can install binary packages from the **r
 1. Make sure you have a working ROS 2 installation from Debian packages (see :doc:`../Installation`).
 
 2. Edit (with sudo) the file ``/etc/apt/sources.list.d/ros2.list`` and change ``ros2`` with ``ros2-testing``.
-   For example, on Ubuntu Jammy the contents should look like the following:
+   For example, on Ubuntu Noble the contents should look like the following:
 
    .. code-block:: sh
 
-      # deb http://packages.ros.org/ros2/ubuntu jammy main
-      deb http://packages.ros.org/ros2-testing/ubuntu jammy main
+      # deb http://packages.ros.org/ros2/ubuntu noble main
+      deb http://packages.ros.org/ros2-testing/ubuntu noble main
 
 3. Update the ``apt`` index:
 
@@ -53,8 +53,8 @@ For Debian-based operating systems, you can install binary packages from the **r
 
    .. code-block:: sh
 
-      deb http://packages.ros.org/ros2/ubuntu jammy main
-      # deb http://packages.ros.org/ros2-testing/ubuntu jammy main
+      deb http://packages.ros.org/ros2/ubuntu noble main
+      # deb http://packages.ros.org/ros2-testing/ubuntu noble main
 
    and doing an update and upgrade:
 

diff --git a/source/Installation/Ubuntu-Install-Debians.rst b/source/Installation/Ubuntu-Install-Debians.rst
@@ -9,7 +9,7 @@ Ubuntu (Debian packages)
    :depth: 2
    :local:
 
-Debian packages for ROS 2 {DISTRO_TITLE_FULL} are currently available for Ubuntu Jammy.
+Debian packages for ROS 2 {DISTRO_TITLE_FULL} are currently available for Ubuntu Noble.
 The Rolling Ridley distribution will change target platforms from time to time as new platforms are selected for development.
 The target platforms are defined in `REP 2000 <https://ros.org/reps/rep-2000.html>`__.
 Most people will want to use a stable ROS distribution.
@@ -19,7 +19,7 @@ Resources
 
 * Status Page:
 
-  * ROS 2 {DISTRO_TITLE} (Ubuntu Jammy): `amd64 <http://repo.ros2.org/status_page/ros_{DISTRO}_default.html>`__\ , `arm64 <http://repo.ros2.org/status_page/ros_{DISTRO}_ujv8.html>`__
+  * ROS 2 {DISTRO_TITLE} (Ubuntu Noble): `amd64 <http://repo.ros2.org/status_page/ros_{DISTRO}_default.html>`__\ , `arm64 <http://repo.ros2.org/status_page/ros_{DISTRO}_ujv8.html>`__
 * `Jenkins Instance <http://build.ros2.org/>`__
 * `Repositories <http://repo.ros2.org>`__
 
@@ -58,13 +58,6 @@ Update your apt repository caches after setting up the repositories.
 
 .. include:: _Apt-Upgrade-Admonition.rst
 
-.. warning::
-
-   Due to early updates in Ubuntu 22.04 it is important that ``systemd`` and ``udev``-related packages are updated before installing ROS 2.
-   The installation of ROS 2's dependencies on a freshly installed system without upgrading can trigger the **removal of critical system packages**.
-
-   Please refer to `ros2/ros2#1272 <https://github.com/ros2/ros2/issues/1272>`_ and `Launchpad #1974196 <https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1974196>`_ for more information.
-
 Desktop Install (Recommended): ROS, RViz, demos, tutorials.
 
 .. code-block:: bash
@@ -123,12 +116,6 @@ Next steps
 
 Continue with the :doc:`tutorials and demos <../../Tutorials>` to configure your environment, create your own workspace and packages, and learn ROS 2 core concepts.
 
-Use the ROS 1 bridge (optional)
--------------------------------
-
-The ROS 1 bridge can connect topics from ROS 1 to ROS 2 and vice-versa.
-See the dedicated :doc:`document <../../How-To-Guides/Using-ros1_bridge-Jammy-upstream>` on how to build and use the ROS 1 bridge.
-
 Troubleshoot
 ------------
 

diff --git a/source/Installation/_rosdep_Linux_Mint.rst b/source/Installation/_rosdep_Linux_Mint.rst
@@ -1 +1 @@
-**Note**: If you're using a distribution that is based on Ubuntu (like Linux Mint) but does not identify itself as such, you'll get an error message like ``Unsupported OS [mint]``. In this case append ``--os=ubuntu:jammy`` to the above command.
+**Note**: If you're using a distribution that is based on Ubuntu (like Linux Mint) but does not identify itself as such, you'll get an error message like ``Unsupported OS [mint]``. In this case append ``--os=ubuntu:noble`` to the above command.
diff --git a/source/Releases/Release-Rolling-Ridley.rst b/source/Releases/Release-Rolling-Ridley.rst
@@ -22,7 +22,7 @@ Rolling Ridley is currently supported on the following platforms:
 
 Tier 1 platforms:
 
-* Ubuntu 22.04 (Jammy): ``amd64`` and ``arm64``
+* Ubuntu 24.04 (Noble): ``amd64`` and ``arm64``
 * Windows 10 (Visual Studio 2019)
 
 Tier 3 platforms:

diff --git a/source/The-ROS2-Project/Contributing/Build-Farms.rst b/source/The-ROS2-Project/Contributing/Build-Farms.rst
@@ -54,7 +54,7 @@ The names of the jobs encode their type and purpose: [1]_
    * ``{distro}src_{platf}__{package}__{platform}__source`` build source packages of releases
    * ``{distro}bin_{platf}__{package}__{platform}__binary`` build binary packages of releases
 
-   For instance, the binary packaging job of rclcpp on ROS 2 Iron (running on Ubuntu Jammy amd64) is named ``Ibin_uJ64__rclcpp__ubuntu_jammy_amd64__binary``.
+   For instance, the binary packaging job of rclcpp on ROS 2 Rolling (running on Ubuntu Noble amd64) is named ``Rbin_uN64__rclcpp__ubuntu_noble_amd64__binary``.
 
 * devel jobs:
 
@@ -64,7 +64,7 @@ The names of the jobs encode their type and purpose: [1]_
 
    * ``{distro}pr__{package}__{platform}`` perform a CI build for a pull request
 
-   For instance, the PR job for rclcpp on ROS 2 Iron (running on Ubuntu Jammy amd64) is named ``Ipr__rclcpp__ubuntu_jammy_amd64``.
+   For instance, the PR job for rclcpp on ROS 2 Rolling (running on Ubuntu Noble amd64) is named ``Rpr__rclcpp__ubuntu_noble_amd64``.
 
 Execution
 .........

diff --git a/source/The-ROS2-Project/Contributing/Developer-Guide.rst b/source/The-ROS2-Project/Contributing/Developer-Guide.rst
@@ -696,7 +696,7 @@ Additionally, we test all pull requests against these platforms before merging.
 This is the current set of target platforms and architectures, though it evolves overtime:
 
 
-* Ubuntu 22.04 Jammy
+* Ubuntu 24.04 Noble
 
   * amd64
   * aarch64

diff --git a/source/The-ROS2-Project/Features.rst b/source/The-ROS2-Project/Features.rst
@@ -8,7 +8,7 @@ Features Status
 ===============
 
 The features listed below are available in the current ROS 2 release.
-Unless otherwise specified, the features are available for all supported platforms (Ubuntu 22.04 (Jammy), Windows 10), DDS implementations (eProsima Fast DDS, RTI Connext DDS, and Eclipse Cyclone DDS) and programming language client libraries (C++ and Python).
+Unless otherwise specified, the features are available for all supported platforms (Ubuntu 24.04 (Noble), Windows 10), DDS implementations (eProsima Fast DDS, RTI Connext DDS, and Eclipse Cyclone DDS) and programming language client libraries (C++ and Python).
 For planned future development, see the :doc:`Roadmap <Roadmap>`.
 
 .. list-table::
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		Note: If you're using a distribution that is based on Ubuntu (like Linux Mint) but does not identify itself as such, you'll get an error message like ``Unsupported OS [mint]``. In this case append ``--os=ubuntu:jammy`` to the above command.
		Note: If you're using a distribution that is based on Ubuntu (like Linux Mint) but does not identify itself as such, you'll get an error message like ``Unsupported OS [mint]``. In this case append ``--os=ubuntu:noble`` to the above command.