1
$\begingroup$

Assuming you maintain only a single ROS2 package version, i.e. you always keep the sources identical across all ROS2 distros, and you want to release all packages with the same version number on all ROS2 distros. How do you set up the tracks and version numbers when running bloom-release?

$\endgroup$

1 Answer 1

1
$\begingroup$

Here is @chrisbedard's answer, which boils down to this:

  • Maintain separate tracks for each distro
  • Keep only a single branch (named e.g "release") that holds the most recently released version, including the CHANGELOG.rst
  • To create a new release, git checkout release && git merge <devel_branch>, then run catkin_generate_changelog and catkin_prepare_release as usual.
  • Now run bloom-release separate for each distro, but when configuring the track, set the upstream branch identical for all distros, e.g. "release". Note: if you want to switch to this method, bloom-release has a --edit-track feature.
$\endgroup$
1
  • $\begingroup$ Thanks for posting this Q&A here! $\endgroup$ Commented Jul 1 at 16:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.