This page will explain how the sbg_driver should be released, according to these docs :
Once all changes have been committed in the master branch, and the driver is ready for release, update the changelog file.
In the source directory of the driver, execute the following command. Clean up the changelog file, but do not touch the "Forthcoming" title, it will be updated by bloom during the release process. Once it has been modified, commit the changelog.
catkin_generate_changelog
Use the catkin command to prepare the driver for release. You can add the '--bump' option, to choose the version increment. By default, it will increase the patch version, 2.0.2 -> 2.0.3
catkin_prepare_release --bump {major, minor, patch}
A completed prerelease test is a quite good guarantee that the package will run perfectly. Follow the instructions from the prerelease doc pages. The following command could be used to generate the prerelease executables.
generate_prerelease_script.py \
https://raw.githubusercontent.com/ros-infrastructure/ros_buildfarm_config/production/index.yaml \
melodic default ubuntu bionic amd64 sbg_driver --level 0 --output-dir .
Execute the bloom command to release, for every required rosdistro (Melodic, Kinetic). These command will ask for automatic push to the sbg_driver_release repository, and pull request to the rosdistro repository.
bloom-release sbg_driver --rosdistro <rosdistro>
In case you want to release the driver for a new distro, use the following command, and refer to the documentation page to release a package for the first time.
bloom-release --rosdistro <ros_distro> --track <ros_distro> sbg_driver --edit