From 96373561331e21ec65915736d41f536b991e92df Mon Sep 17 00:00:00 2001 From: Sean McGinnis Date: Mon, 16 Dec 2019 13:53:52 -0600 Subject: [PATCH] Fix propose-update-constraints job name in docs The propose-update-constraints job was referred to as propose-upper-constraints. Update name to make it a little easier if someone is looking for references to the actual job. Change-Id: I707b2a498af491c9d2e481ed1880ad74839c9389 Signed-off-by: Sean McGinnis --- doc/source/reference/reviewer_guide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/source/reference/reviewer_guide.rst b/doc/source/reference/reviewer_guide.rst index 2184a617b3..ba970ebb4e 100644 --- a/doc/source/reference/reviewer_guide.rst +++ b/doc/source/reference/reviewer_guide.rst @@ -232,7 +232,7 @@ and uploads it. .. ttx has a nice diagram of that, insert it here After a Python package release is uploaded, the job -``propose-upper-constraints`` submits a change to +``propose-update-constraints`` submits a change to ``openstack/requirements`` to update the ``upper-constraints.txt`` list. The constraints list is used along with the actual requirements list to tell the jobs which versions of which packages to