diff --git a/source/How-To-Guides/Releasing/Release-Team-Repository.rst b/source/How-To-Guides/Releasing/Release-Team-Repository.rst index 7a90a0dce15..bc0dd92c211 100644 --- a/source/How-To-Guides/Releasing/Release-Team-Repository.rst +++ b/source/How-To-Guides/Releasing/Release-Team-Repository.rst @@ -41,8 +41,7 @@ if a release team already exists for your project but you are not part of it. Start a new release team ^^^^^^^^^^^^^^^^^^^^^^^^ -Fill the `New Release Team issue `_ issue template -if no release team exists for your project yet, request for a new release team to be created. +If no release team exists for your project yet, fill out the `New Release Team issue `_ issue template to request one be created. .. _what-is-a-release-repository: @@ -61,7 +60,7 @@ Having a release repository separate from your source code repository is a requi Create a new release repository ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ -If your repository is new to the ROS community, you should first open a pull request on `ros/rosdistro `_ adding a ``source`` entry for your repository. +If your repository is new to the ROS community, you should first open a pull request on `ros/rosdistro `_ adding a ``source`` entry for your repository (e.g. https://github.com/ros/rosdistro/pull/39513). The review process for the rosdistro database will ensure your repository and packages conform to the `REP 144 package naming conventions `_ and other requirements before release. Once your package name has been approved and merged, fill in the `Add New Release Repositories issue `_ issue template if you don't have a release repo for your project yet.