The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
The python-rosrelease package is used for making "dry" (non-catkin) releases to Fuerte and Groovy. I believe it also works for Electric. The command usage is:
$ rosrelease-legacy <stack> <version> <release-name>
| | 2 | No.2 Revision |
The Ubuntu python-rosrelease package is used for making "dry" (non-catkin) releases to Fuerte and Groovy. I believe it also works for Electric. The command usage is:
$ rosrelease-legacy <stack> <version> <release-name>
| | 3 | No.3 Revision |
The Ubuntu python-rosrelease python-rosrelease package is used for making "dry" (non-catkin) releases to Fuerte and Groovy. I believe it also works for Electric. The command usage is:
$ rosrelease-legacy <stack> <version> <release-name>
| | 4 | add link to pre-release page |
The Ubuntu python-rosrelease package is used for making "dry" (non-catkin) releases to Fuerte and Groovy. I believe it also works for Electric. The command usage is:
$ rosrelease-legacy <stack> <version> <release-name>
EDIT: Before releasing a package you should run the pre-release tests.
There is now a new pre-release page which handles all currently supported ROS versions.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.