Release ROS Stacks
Contents
ROS has a release infrastructure that enables you to take your ROS stacks and distribute it to the rest of the community.
What it does:
Create versioned releases of ROS stacks.
Submit tarballs to the ROS debian packaging system for inclusion in a ROS distribution, which enables them to be installed by apt-get.
Compatibility
This only works with SVN or Mercurial or Git-based code repositories. It should be simple to extend it to other SCM tools and we welcome bzr users who are willing to contribute patches.
We only have one prohibition on stacks being released:
they may not access external source control repositories during the build process, e.g. by using svn_checkout.mk. This generally is only used in thirdparty library integration.
Please see this mailing list thread for more details.
Doing a release
Before you do any release, first you need to follow the setup instructions.
Once you're setup, go ahead and do the release.
Release maintainer list
Please sign up for the (low-volume) ros-release mailing list to receive status updates on releases.
Automated build tests
For more information on the automated build tests that get run on Hudson, see regression_tests.
System Status