Skip to content

Home

Jump to bottom
Olivier Michel edited this page Sep 27, 2022 · 19 revisions

Release Status

Whenever a change is committed to the master branch of this repository, we should create a new version and ensure it is listed for the next sync of the ROS Noetic distribution. The new version of the Webots ROS package should appear in the SYNC list (usually at the bottom) with the following icons:

image

Updating the Packages

Make sure python command point to python2 and not python3.

Create tag

Make sure that every branch version is up to date and create a tag corresponding to the version (specified in package.xml):

git tag -a 2.1.1 -m "Version 2.1.1"
git push origin 2.1.1

Install ROS

  • Ubuntu 18.04 and ROS melodic are no more supported.
  • On Ubuntu 20.04 and up, you should install ROS noetic.

Run:

sudo rosdep init
rosdep update

Bloom Release

Launch bloom release to update the content of the webots_ros-release repo. Here is an example for noetic but the same procedure is valid for other versions of ROS (melodic and noetic).

bloom-release --rosdistro noetic --track noetic webots_ros --edit

You can say yes to all the default options (except for last one), which should be:

  • Repository Name: webots_ros
  • Upstream Repository URI: https://github.com/cyberbotics/webots_ros.git
  • Upstream VCS Type: git
  • Version & Release Tag: should match the version, e.g, 2.1.1 (or {auto})
  • Upstream Devel Branch: noetic
  • ROS Distro: noetic
  • Patches Directory: None
  • Release Repository Push URL: None (This indicates that the default release url should be used.)
  • Releasing complete, push to release repository?: Y
  • Would you like to create an OAuth token now: n

ROS-Distro update

Create a PR on https://github.com/ros/rosdistro (the diff is shown at the end of the bloom-release procedure).

Clone this wiki locally