Skip to content
David Mansolino edited this page Aug 23, 2019 · 20 revisions

Updating the Packages

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 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).

bloom-release --rosdistro crystal --track crystal webots_ros2 webots_ros2_core webots_ros2_desktop webots_ros2_examples webots_ros2_msgs webots_ros2_universal_robot [--edit]

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

  • Repository Name: webots_ros2
  • Upstream Repository URI: https://github.com/omichel/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).

Clone this wiki locally