Meta ticket tracking things to be done for the Bouncy release

• Kick-off:

  • REP-2000 for bouncy @mikaelarguedas: [REP-2000] Add bouncy ros-infrastructure/rep#174

• Infrastructure:

  • upgrade linux buildfarm hosts @nuclearsandwich
  • configure build.ros2.org smtp @nuclearsandwich
    • contact AWS to get SMTP usage whitelisted
  • create Bouncy distro: @mikaelarguedas
    • ros2/rosdistro: add bouncy distro rosdistro#79
    • ros2/ros_buildfarm_config: add bouncy build files ros_buildfarm_config#5
    • Deploy bouncy management jobs to build.ros2.org
    • update arm node label to pick up bouncy jobs: buildagent_arm64 || bouncy_binarydeb_ubv8
  • Release bootstrap packages
    • ament_package ament_package: 0.5.0-0 in 'bouncy/distribution.yaml' [bloom] rosdistro#81
    • ament_cmake ament_cmake: 0.5.0-1 in 'bouncy/distribution.yaml' [bloom] rosdistro#84
    • ros_environment ros_environment: 2.1.0-0 in 'bouncy/distribution.yaml' [bloom] rosdistro#87
    • ros_workspace ros_workspace: 0.5.0-1 in 'bouncy/distribution.yaml' [bloom] rosdistro#86

• Bionic support: details tracked at Target bionic (meta) #481 @mikaelarguedas

• Packaging:

  • Implement solution for allowing to opt out from multi rmw install

    • with Debian packages: @nuclearsandwich
      possibilities:
      • put only build_depend on the "optional" rmws
      • inject a Recommends Suggests for the "optional" rmws
    • on macOS from fat archives Multi-RMW OS X binary still requires users have all RMW impls installed #437

  • Extract catkin_prepare_release from catkin to be used by ROS 2 users @dirk-thomas move catkin_prepare_release and dependencies from catkin ros-infrastructure/catkin_pkg#216

    • also not a blocker since the script is available when sourcing ROS 1 as a temporary workaround

  • Audit patches on release repositories

    • NO patch needed: No patch needed for Bouncy ros2-gbp/ament_package-release#1
    • https://github.com/ros2-gbp/console_bridge-release: We can keep the existing patch as long as we don't create a vendor package for it
    • https://github.com/ros2-gbp/fastcdr-release
      • PR adding package.xml: [bouncy] add package.xml ros2-gbp/fastcdr-release#1
        While we could have kept the ardent patch, the dependency on ament_cmake seemed unnecessary so I removed it and submitted another patch file for bouncy
    • https://github.com/ros2-gbp/fastrtps-release
      • existing patch should be kept as is as Fast-RTPS dependencies didn't change
      • Still need to patch debian/rules.em to build with -DSECURITY after running bloom for the first time
      • Remove examples from installation PR: Remove fastrtps examples from installation. ros2-gbp/fastdds-release#4
    • NO patch needed: [map_server] Bouncy: no need to inject dependency on boost on bionic  ros2-gbp/navigation-release#2
    • https://github.com/ros2-gbp/resource_retriever-release PR: depend on curl (libcurl-dev, curl) for packaging ros/resource_retriever#25
    • https://github.com/ros2-gbp/ros1_bridge-release.
      • PR adding dependencies for the packages we want to build the bridge for: [bouncy] add package.xml patch for bouncy ros2-gbp/ros1_bridge-release#1
      • PR adding melodic dependencies and sourcing melodic environment during build Incorporate melodic workspace and dependencies. ros2-gbp/ros1_bridge-release#2
    • https://github.com/ros2-gbp/poco_vendor-release PR: add package.xml for poco_vendor poco_vendor#15
    • https://github.com/ros2-gbp/tinyxml_vendor-release PR: add package.xml tinyxml_vendor#10
    • https://github.com/ros2-gbp/rosidl_typesupport-release
      • rosidl_typesupport_c: add Suggests on vendor typesupport_c packages
      • rosidl_typesupport_cpp: add Suggests on vendor typesupport_cpp packages
    • https://github.com/ros2-gbp/rmw_opensplice-release No patches.
    • https://github.com/ros2-gbp/rmw_implementation-release
      • add runtime depend on any one rmw implementation commit link
    • https://github.com/ros2-gbp/rviz-release patches for vendor shlibdeps
      • rviz2 (commit)
      • rviz_assimp_vendor (commit)
      • rviz_common (commit)
      • rviz_default_plugins (commit)
      • rviz_ogre_vendor (commit)
      • rviz_rendering (commit)
      • rviz_rendering_tests (commit)
      • rviz_visual_testing_framework (commit)
      • rviz_yaml_cpp_vendor (commit)
    • add links to any other patches applied in the release repo (e.g. suggests) @nuclearsandwich

  • Propagate ignored files

    • propagate ignored file for bouncy ros2-gbp/urdf-release#1
    • propagate ignored file for bouncy ros2-gbp/rviz-release#2
    • propagate ignored file for bouncy ros2-gbp/orocos_kinematics_dynamics-release#1
    • propagate ignored file for bouncy ros2-gbp/navigation-release#1
    • propagate ignored file for bouncy ros2-gbp/kdl_parser-release#1
    • propagate ignored file for bouncy ros2-gbp/joystick_drivers-release#1
    • propagate ignored file for bouncy ros2-gbp/geometry2-release#1
    • propagate ignored file for bouncy ros2-gbp/cartographer_ros-release#1
    • https://github.com/ros2-gbp/vision_opencv-release (likely not propagate anything and leave it to the Intel team to pick what to ignore or release)

• colcon:

  • release a new version of the colcon packages
  • provide Debian packages
    • import in the ROS apt repos
    • import in the ROS2 apt repos
  • merge design PR update universal build tool article to reflect decision to use colcon design#168
  • custom logic to avoid leading spaces consider custom parsing logic to avoid leading space for nested arguments colcon/colcon-core#36
    only after that has been addressed:
    • update wiki to refer to colcon everywhere Update ROS 2 wiki to use colcon instead of ament_tools #511
    • deprecate ament_tools repo post Bouncy release
  • add devel / PR jobs add source build file for Bouncy ros_buildfarm_config#7

• Dependency management:

  • ASIO: SRU submitted, keep using system version for now
  • Assimp: waiting on upstream:
    • alternative: keep vendoring it for all platforms
    • workaround to be able to build against upstream: work around libassimp-dev bug rviz#288
  • console_bridge: create a vendor package and use upstream on MacOS and Bionic (optional)
    - [ ] curl: @wjwwood to confirm if vendoring it is still needed the choco package on windows doesn't provide dev libraries
  • poco: use upsream on MacOS: update CI machines
  • tinyxml2: choco: Update custom choco package to 6.0.0
  • eigen: choco: use 3.3.4 (stable) to avoid https://discourse.ros.org/t/ros-answers-kinetic-uses-unstable-eigen3-on-ubuntu-16-04/4425
  • asio: choco: use 1.12.1

• Documentation

  • Update tutorials
  • update installation instructions
  • remove mentions to beta1 or earlier from the wiki

• T-shirt campaign

• C-Turtle Name