|Title:||ROS 1.4 Release Schedule|
|Author:||Ken Conley <kwc at willowgarage.com>|
This REP describes the ROS 1.4 release schedule. The schedule primarily concerns itself with large-impact additions. For general high-level planning, see the ROS Roadmap . As per general ROS stack development guidelines, features for ROS 1.4 will be developed in the ROS 1.3.x release cycle and finalized for ROS 1.4.0.
The schedule below is tentative. The target date for the ROS Diamondback distribution in February, 2011. Features for ROS 1.4 may be shifted to ROS 1.6 as appropriate to meet the Diamondback distribution release schedule.
Optional features are "nice-to-haves" but are not considered critical path for this release, nor do they impact downstream components. They will be scheduled if time permits.
The ROS 1.4 release has several main thrusts:
Of these thrusts, separation of the ROS stack is expected to have the broadest impact. It should enable the ROS packaging and build system to be used outside of ROS, and it will also help with integration on other platforms (e.g. embedded, OS X, Windows). The motivation and rationale are better described in REP 100 .
Incorporating community stacks is a priority as there are over 30 ROS repositories now. Having a shared mechanism for release and distribution will enable the community to more easily exchange libraries, including helping address issues of versioning and system configuration. This will also be a test for future developments in the release system, such as supporting alternate distributions (e.g. distributions for specific robot platforms or research areas).
rosh and rxlab are being designed as complementary tools for rapid prototyping. rosh is a Python- and IPython-based framework with that enables tab-completion on ROS resources (e.g. topics, services, parameters, actions, transforms. rxlab is a Python GUI framework that enables creation of "networks" within a single Python process to do a variety of tasks, such as creating image-processing pipelines. It is similar to frameworks such as Simulink, but is targeted at ROS libraries like OpenCV. rosh and rxlab are being built on top of the existing Python toolchain as they provide many of the necessary libraries for dynamic introspection in a ROS graph.
The ROS backwards compatibility guidelines require that ROS 1.4 being fully backwards compatible with ROS 1.2. The main concern for this release will be ensuring that the separation of the ROS stack into three stacks will not an existing code to break. This will likely require additional resources and files to remain with the base "ros" stack in the 1.4 release, but deprecated so that they can be removed in the 1.6 release.
|||ROS Roadmap (http://ros.org/wiki/ROS/Roadmap)|
|||(1, 2) REP 100 (http://ros.org/reps/rep-0100.html)|
This document has been placed in the public domain.