Skip to content

Home

Jump to bottom
iamtesch edited this page Jan 30, 2019 · 6 revisions

Welcome to the HEBI-ROS wiki!

Release Process (note -- this differs from the standard bloom process because we are using the gitflow workflow.

  • Ensure all tests pass, and code is ready for release
  • Run a pre-release, making sure it succeeds, using the following commands:
mkdir -p /tmp/prerelease_job
cd /tmp/prerelease_job
generate_prerelease_script.py \
  https://raw.githubusercontent.com/ros-infrastructure/ros_buildfarm_config/production/index.yaml \
  kinetic default ubuntu xenial amd64 \
  --custom-repo \
    hebiros:git:https://github.com/HebiRobotics/HEBI-ROS.git:develop \
  --level 1 \
  --output-dir ./
./prerelease.sh
  • NOTE: this should be done for each package you have made updates to! The above example is just for hebiros. Packages with dependencies on other packages you are updating might need to be handled specially; this should be looked into and documented! Also, note that this is for kinetic/xenial; in the future, we will want to release for melodic/bionic as well.
  • Open pull request INTO DEVELOP with version number change in package.xml and update to CHANGELOG.rst (in each package). Wait before merging to ensure the Travis CI builds finish successfully. Note that you can use catkin_generate_changelog to help with the generation of the CHANGELOG.rst file.
  • Wait for the PR to be approved, and merge into develop.
  • Open a pull request INTO MASTER FROM DEVELOP, titled with the version number + with the concatenated changelog updates in the body.
  • Wait for the PR to be approved, and merge into master.
  • Create a tag with the version number (e.g., 2.0.1) on master. Note this should be an annotated tag; you can do this locally and push to the server with:
git tag -a <version number goes here>
<PASTE THE CONCATENATED CHANGELOGS AS THE COMMIT MESSAGE>
git push --follow-tags
Clone this wiki locally