ROS 1.0 has been released!
We also released pr2_simulator 1.0 today, which completes our 1.0 release cycle.
To put this all in context, getting to 1.0 meant completing:
- 203 ROS software tutorials
- 29 ROS Stacks at 1.0 status, which contain a total of 186 ROS Packages
- 21 Use Cases, requiring well over a hundred user studies
Development on ROS began a little over two years ago. There have been many changes since those early days, and what started as a little project with a couple of developers has blossomed into a vibrant community supporting a wide variety of robots, big and small, academia and industry.
We hope that this 1.0 release will help the community even more and that you all will continue to participate and contribute.
While ROS 1.0 is an important step, we're even more excited by the many other libraries that have reached 1.0, including:
- Core libraries: common 1.0, common_msgs, diagnostics 1.0, geometry 1.0, robot_model 1.0
- Visualization tools: visualization 1.0, visualization_common 1.0
- Drivers: driver_common 1.0, imu_drivers 1.0, joystick_drivers 1.0, laser_drivers 1.0, sound_drivers 1.0
- Navigation: navigation 1.0, slam_gmapping 1.0
- Simulation: physics_ode 1.0, simulator_stage 1.0, simulator_gazebo 1.0, pr2_simulator 1.0
- Perception: image_common 1.0, image_pipeline 1.0, laser_pipeline 1.0, vision_opencv 1.0
- PR2: pr2_common 1.0, pr2_controllers 1.0, pr2_gui 1.0, pr2_mechanism 1.0, pr2_power_drivers 1.0, pr2_ethercat_drivers 1.0
We look forward to your feedback and improvements on these building blocks.
-- your friendly neighborhood ROS 1.0 team
The focus of changes for this release was on bug fixes, cleanup, and resolving any remaining API issues.
There was one deprecated API removed in this final release, and will require migration for code not yet updated:
* roscpp: Removed deprecated 3-argument versions of
rospy now also warns on illegal names. We have been introducing more name strictness in ROS. ROS auto-generates source code of messages and services. The name strictness ensures that source code can be validly generated for these types. There are also potential features in our roadmap that will require name strictness as well.
For a complete list of changes in this release, please see the change list.