ROS Resources: Documentation | Support | Discussion Forum | Service Status | Q&A answers.ros.org

Preparing for Dashing sync and patch release: 2020-03-17

It’s time for another Dashing sync and looking at the board I think we’re ready for a patch release as well.

There are a good number of new packages from the community ready for sync:

If you find a regression when testing, please report it upstream and leave a comment here so we can track it leading up to the sync.

Please get your releases in for this sync as early as you can, and on 2019-03-10 we’ll hold all rosdistro PRs unless they fix reported regressions.

2 Likes

I’ve decided to push the rosdistro freeze and patch release date out to Tuesday 2020-03-17. There are still a few backports pending in the ROS 2 base that I want to give some time in the testing repository before the sync.

2 Likes

The initial CI for the patch release revealed a build failure in osrf_testing_tools_cpp on Windows. We’re working to resolve that with https://github.com/osrf/osrf_testing_tools_cpp/pull/43 once that’s merged and released I’ll update Dashing and re-trigger the total CI. I expect the patch release will come tomorrow rather than today.

The release of osrf_testing_tools_cpp went through last night and we’re waiting for armhf builds to finish before the sync as well as for final CI to come back for the binary archives. For those following along at home and thinking CI looks a little dire. There are a few general compounding issues affecting the “green” status of Dashing.

  • Linter-only changes are not backported. To reduce churn, we don’t backport linter changes exclusively. We may update a package to fix linter warnings when backporting other fixes to allow CI to go green for that backport. However, we are constantly updating the linter versions on ci.ros2.org so there is usually drift between green circa a distribution’s initial release and the current state of CI.
  • Recent updates to ci.ros2.org exposed issues in test output generated by ament_lint and ament_cmake causing job “failure” during the test analysis phase. The test-result output in the job log is the source of truth for these builds.
    These changes have yet to be backported into Dashing and Eloquent. They were late enough that I didn’t want to delay this release cycle for them but I will backport them for the next Dashing and Eloquent patch releases.
  • macOS Mojave is not a supported platform. There are a growing number of test failures on macOS. I like to keep building on macOS because I want to know when the build actually begins to fail but Sierra was the supported macOS platform for Dashing and when support for Sierra ended we stopped producing macOS binaries. If a community member wishes to backport fixes for test failures on Mojave I will do my best to help find reviewers.
  • Cyclone DDS failures do not block releases. Cyclone DDS was not part of Dashing’s initial release and is not a tier 1 or 2 supported middleware for the Dashing release so test failures related to Cyclone may occur without blocking the release process. I believe there are plans to update the version of Cyclone DDS used in Dashing so stay tuned for future syncs and patch releases.

The release is out!