The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
Both tutorials work together in tandem, although they could be improved to peel back a layer and explain why some steps repeat work. And work is repeated between them.
Bloom takes inspiration from git's design with a "plumbing and porcelain" model. The git-bloom-release command
is in Bloom's plumbing category and using it during the third-party release process is the most expedient way to make sure that the changes made to the project are propagated where they need to be.
As a side note, there are also a lot of local branches in my local clone of the release repo, which git-bloom-release didn't seem to push to Github.
As a plumbing command, it isn't fully automatic, so we should probably update that tutorial suggesting that you push the generated branches and tags to the release repository and then finalize the release by running the full bloom-release ... command as described in the first-time release tutorial.
What's the next step in releasing the package? Do I have to manually open a PR for rosdistro? What else do I have to do?
Because of the previous run, this may result in a package revision (sometimes called the debian increment) of 2 rather than 1 for a first release but that is completely benign. Running a full bloom-release command even though it performs some overlapping work is definitely recommended, especially at the tutorial level since the bloom-release command will run the comprehensive process including populating the rosdistro patch and submitting the pull request.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
