Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion source/How-To-Guides/Releasing/Release-Team-Repository.rst
Original file line number Diff line number Diff line change
Expand Up @@ -42,7 +42,7 @@ Start a new release team
^^^^^^^^^^^^^^^^^^^^^^^^

Fill the `New Release Team issue <https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&template=new_release_team.md&title=Add+release+team>`_ 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 by requesting for a new release team to be created.
Comment thread
Ryanf55 marked this conversation as resolved.
Outdated

.. _what-is-a-release-repository:

Expand All @@ -62,6 +62,7 @@ Create a new release repository
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

If your repository is new to the ROS community, you should first open a pull request on `ros/rosdistro <https://github.com/ros/rosdistro>`_ adding a ``source`` entry for your repository.
An example can be seen `here <https://github.com/ros/rosdistro/pull/39513>`_.
Comment thread
Ryanf55 marked this conversation as resolved.
Outdated
The review process for the rosdistro database will ensure your repository and packages conform to the `REP 144 package naming conventions <https://www.ros.org/reps/rep-0144.html>`_ and other requirements before release.
Once your package name has been approved and merged, fill in the `Add New Release Repositories issue <https://github.com/ros2-gbp/ros2-gbp-github-org/issues/new?assignees=&labels=&template=new_release_repository.md&title=Add+new+release+repositories>`_ issue template
if you don't have a release repo for your project yet.
Expand Down