For an Ardent patch release 1 we will cherry-pick the minimal changes which are necessary to address important issues. The high level goals are:

• provide rviz for Windows
• fix problem(s) in FastRTPS, e.g. [solved e90e4b7] eProsima Fast-RTPS Segmentation Fault  eProsima/Fast-DDS#181
• fix problem with include path order in rosidl
• Provide ros_environment for the env vars specified in REP 149

We will do the following:

• Create PRs using a to be created source branch named ardent-patch1 targeting the existing ardent branch:
  • rviz @wjwwood (Ardent patch1 release rviz#188)
  • pluginlib @wjwwood (Ardent patch1 release ros/pluginlib#98)
  • resource_retriever @wjwwood (Ardent patch1 release ros/resource_retriever#18)
  • fastrtps @dirk-thomas (Ardent patch1 #455)
  • rosidl @mikaelarguedas (Ardent patch release rosidl#262)
  • ros_environment @dirk-thomas (this doesn't need a PR, the ardent branch is already the state we want to release)
• Check if any packages should be updated on the macOS / Windows nodes (and if it affects the instructions): @wjwwood
• Roll some fat archives to check they "address" the problems.
• Merge the PRs.
• Make a patch release in the affected repos.
• Do the bloom releases.
  • @nuclearsandwich mentioned addressing a minor issue in the FastRTPS manifest which can be fixed along the way.
• Upload the archives under a new release in the ros2 repo.
• Announce the patch release with a name like ardent-2018-02-xx.