Home

Updating the Packages

Tag

Make sure that every branch version is up to date, the changelogs date are set and create a tag corresponding to the version (specified in the package.xml files, make also sure the version in these files is up to date):

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

Bloom Release

Launch bloom release to update the content of the webots_ros2-release repo. Here is an example for Crystal but the same procedure is valid for other versions of ROS (e.g. Dashing), we ask for the webots_ros2_desktop package because this package has dependencies on all the others.

bloom-release --rosdistro crystal --track crystal webots_ros2_desktop --edit

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

• Release repository url: https://github.com/cyberbotics/webots_ros2-release.git
• Repository Name: webots_ros2
• Upstream Repository URI: https://github.com/cyberbotics/webots_ros2.git
• Upstream VCS Type: git
• Version & Release Tag: should match the version (or {auto})
• Upstream Devel Branch: crystal
• ROS Distro: crystal
• 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).