ROS Release Progress

[Sharwin24]

This issue will track notes, issues, and feedback from going through the ROS release tutorial and all of the relevant steps.

Joining a Release Team

Northwestern MSR already has a release team and a github issue was created by Matt to add me

Licensing

The Apache 2.0 License was picked since it is recommended in the tutorial for indexing your first package. This License is applied to all of the packages in this repo.

Changelog

The Changelog was generated by running this command in the repo root:

catkin_generate_changelog --all

Bumping the Package Version

This command from the tutorial ensures each package has a unique package number that increases as they are updated

catkin_prepare_release

The potential_fields_library package is pure C++ and has the build_type cmake so it was not recognized by this command. This means we'll have to update the Changelog and package.xml manually so it may be worth it to change the build type if possible

Repository type: git
Found packages: potential_fields, potential_fields_demos, potential_fields_interfaces, potential_fields_library
Warning: the following package are not of build_type ['catkin', 'ament_cmake', 'ament_python'] and may require manual steps to release': potential_fields_library
Continue anyway [y/N]?

Bloom Release

The next step is to run the bloom release tool to add my repo to the ROS build farm. We need to wait until we're ready to make this repo public before running this step since it will automatically create a PR on the rosdistro repository to add my repo to the ros distribution (jazzy)

bloom-release --new-track --rosdistro jazzy --track jazzy potential_fields