Edit on Github

Roadmap

This page describes planned work for ROS 2. The set of planned features and development efforts should provide insight into the overall direction of ROS 2. If you would like to see other features on the roadmap, then please get in touch with us at info@openrobotics.org.

Quarterly Roadmap

Product Readiness is the current focus topic for ROS 2. Over the next two quarters we will concentrate development efforts on topics that make ROS 2 more suitable for use in production scenarios. This includes improving the out-of-box experience for common use cases, documentation improvements, and addressing disparities between ROS 1 and ROS 2.

## 2020 Q3(Jul - Sep)

  • Transport Documentation and Configurations: Describe and document the ROS 2 transport system. Provide default configurations for common uses cases along with documentation. Tracking ticket.

## 2020 Q4(Oct - Dec)

  • Performance Improvements: Analyze rcl*-level performance and resource usage. Develop a strategy to improve performance and reduce resource usage based on data from the analysis. Tracking ticket.

  • Launch: Address current shortcoming in launch, and improve launch testing. Tracking ticket.

  • Documentation Infrastructure: Develop package-level documentation generation infrastructure, deploy documentation, and consolidate existing documentation. Tracking ticket.

Planned releases

Please see the Distributions page for the timeline of and information about future distributions.

Contributing to ROS 2

Looking for something to work on, or just want to help out? Here are a few resources to get you going.

  1. The Contributing guide describes how to make a contribution to ROS 2.

  2. Check out the list of Feature Ideas for inspiration.

  3. For more information on the design of ROS 2 please see design.ros2.org.

  4. The core code for ROS 2 is in the ros2 GitHub organization.

  5. The Discourse forum/mailing list for discussing ROS 2 design is ng-ros.

  6. Questions should be asked on ROS answers, make sure to include at least the ros2 tag and the rosdistro version you are running, e.g. ardent.