Fix topic to be consistent and current release

The topic should be the name of the current release being branched not
the future release being bumped.

Change-Id: Id7086a570539c75bf9f19ff1353f32ee03191f88
Signed-off-by: Thanh Ha <thanh.ha@linuxfoundation.org>

diff --git a/docs/release-process/branch-cutting.rst b/docs/release-process/branch-cutting.rst
index d4b76bf5149ec8fad206c9370f7024c8d9483f98..eb2cd5b62714e9f0e6d5cfa6f8be01342fe9e9a1 100644 (file)
--- a/docs/release-process/branch-cutting.rst
+++ b/docs/release-process/branch-cutting.rst
@@ -101,11 +101,11 @@ Autorelease
 
       git submodule foreach sed -i -e "s#defaultbranch=master#defaultbranch=stable/${CURR_RELEASE,,}#" .gitreview
       git submodule foreach git commit -asm "Update .gitreview to stable/${CURR_RELEASE,,}"
-      git submodule foreach 'git review -t nitrogen-br-cut'
+      git submodule foreach 'git review -t ${CURR_RELEASE,,}-branch-cut'
       sed -i -e "s#defaultbranch=master#defaultbranch=stable/${CURR_RELEASE,,}#" .gitreview
       git add .gitreview
       git commit -s -v -m "Update .gitreview to stable/${CURR_RELEASE,,}"
-      git review -t  ${NEXT_RELEASE,,}-branch-cut
+      git review -t  ${CURR_RELEASE,,}-branch-cut
 
 - Merge all .gitreview patches submitted in the above step. **(Release Engineering Team)**
 - Remove create reference permissions set on gerrit for RE's. **(Helpdesk)**