automatically submit constraint updates after tagging

After we tag a release, automatically propose the constraint
update. This is a stop-gap until we have the release automation going
further, at which point we should move this to its own job to run after
a package has been uploaded to pypi successfully (giving the constraints
tests a better chance of passing).

Change-Id: I1d2118dc93ec08bc2cfcd4b9dec0b30705ab5198
Signed-off-by: Doug Hellmann <doug@doughellmann.com>

release.sh

@@ -105,4 +105,21 @@ else
         $BUGS
 fi
 
+# Try to propose a constraints update for libraries.
+if [[ $INCLUDE_PYPI == "yes" ]]; then
+    title "Proposing constraints update"
+    dist_name=$(python setup.py --name)
+    if [[ -z "$dist_name" ]]; then
+        echo "Could not determine the name of the constraint to update"
+    else
+        cd $MYTMPDIR
+        clone_repo openstack/requirements stable/$SERIES
+        cd openstack/requirements
+        git checkout -b "$dist_name-$VERSION"
+        sed -e "s/^$dist_name.*/$dist_name===$VERSION/" --in-place upper-constraints.txt
+        git commit -a -m "update constraint for $dist_name to $VERSION"
+        git review
+    fi
+fi
+
 exit 0