Revision history [back]

Yes, to former release.yaml is now called distribution.yaml. I have updated the wiki page accordingly.

Your repository will appear in the prerelease list as soon as the ROS distro cache has been updated (which happens roughly every five minutes). (New jobs on the farm (for building Debian packages, documentation and devel tests) are generated once every day (in the late evening PST/PDT)).

The release-line you refer to actually has some context which should make the semantic clearer:

release:
  packages:
  - catkin
  tags:
    release: release/hydro/{package}/{version}
  url: https://github.com/ros-gbp/catkin-release.git
  version: 0.5.89-0

The entry refers to the tag in the git repository which identifies the release for each package. The variables surrounded by curly braces are expanded with each package name and the version number to identify the tag under which the source code of that specific package version can be found (including the Debian control files). For the above example (which contains only a single package) that would be https://github.com/ros-gbp/catkin-release/tree/release/hydro/catkin/0.5.89-0

Yes, to former release.yaml is now called distribution.yaml. I have updated the wiki page accordingly.accordingly (http://wiki.ros.org/action/diff/regression_tests?action=diff&rev1=44&rev2=45).

Your repository will appear in the prerelease list as soon as the ROS distro cache has been updated (which happens roughly every five minutes). (New jobs on the farm (for building Debian packages, documentation and devel tests) are generated once every day (in the late evening PST/PDT)).

The release-line you refer to actually has some context which should make the semantic clearer:

release:
  packages:
  - catkin
  tags:
    release: release/hydro/{package}/{version}
  url: https://github.com/ros-gbp/catkin-release.git
  version: 0.5.89-0

The entry refers to the tag in the git repository which identifies the release for each package. The variables surrounded by curly braces are expanded with each package name and the version number to identify the tag under which the source code of that specific package version can be found (including the Debian control files). For the above example (which contains only a single package) that would be https://github.com/ros-gbp/catkin-release/tree/release/hydro/catkin/0.5.89-0