From a32859cb300832c5ecb69a5e8d2410ff3f623bb9 Mon Sep 17 00:00:00 2001 From: Clark Boylan Date: Thu, 4 Dec 2014 11:55:43 -0800 Subject: [PATCH] Rename voting-testers group to -ci We ended up going with -ci as the name for these third party testing CI group names. Update the doc to reflect this change. Change-Id: If96603f35313dcd6d38cb0e5f1736daa2a4170be --- doc/source/third_party.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/source/third_party.rst b/doc/source/third_party.rst index b9c44c3061..b5a8a19f69 100644 --- a/doc/source/third_party.rst +++ b/doc/source/third_party.rst @@ -197,7 +197,7 @@ Once you have done this you will have everything you need to comment on Gerrit changes from our CI system but you will not be able to vote +/-1 Verified on changes. To get voting rights you will need to get the release group of the project you are testing to add you to their project specific -voting-testers group. Please contact the project in question when you are +-ci group. Please contact the project in question when you are ready to start voting and they can add you to this group. The Jenkins Gerrit Trigger Plugin Way @@ -327,5 +327,5 @@ chance of success if you follow these steps: * If the members of the program you want voting permissions from agree your system should be able to vote, the release group for that program - or project can add you to the voting-testers group specific to that + or project can add you to the -ci group specific to that program/project.