From d13db409df509153270e340120376a887682e516 Mon Sep 17 00:00:00 2001 From: Tully Foote Date: Wed, 11 Jan 2023 05:26:40 -0800 Subject: [PATCH] propose link to using ros2-gbp language (#35729) * propose link to using ros2-gbp language Co-authored-by: Chris Lalancette --- REVIEW_GUIDELINES.md | 1 + 1 file changed, 1 insertion(+) diff --git a/REVIEW_GUIDELINES.md b/REVIEW_GUIDELINES.md index 02e2608584dfe..42b10fb77a301 100644 --- a/REVIEW_GUIDELINES.md +++ b/REVIEW_GUIDELINES.md @@ -43,6 +43,7 @@ There are a few different types of pull requests that are opened against this re * The license must be reflected in the package.xml file of all sub-packages in the repository. * The source repository must be publicly accessible. * The source repository should contain one or more ROS packages (meaning they have a `package.xml` in the source repository). Packages that are not ROS packages can be accepted, but they are rare and require special handling in the release repository. + 1. The best practices for Rolling releases is to use a release repository in the https://github.com/ros2-gbp organization. That way this package can be automatically released from Rolling into the next stable ROS distribution. There are instructions in https://github.com/ros2-gbp/ros2-gbp-github-org/blob/latest/CONTRIBUTING.md describing how to create one. Once the above criteria are satisfied, and the ROS distribution isn't in a "sync freeze", then the PR will be merged.