Always redirect project contributor docs to latest

It doesn't really make sense to publish multiple versions of
contributor documentation, but when contributor documentation is
included in branched projects this is precisely what we end up with.
Luckily, the recent work to standardize project contributor docs
puts them under a consistent subtree of the each project's
documentation, so we can easily match on them.

In order to avoid things like web search results and stale bookmarks
sending unwary users to outdated versions of contributor
information, just always redirect any old series to "latest"
instead.

Change-Id: If55ec3d4e0c98e43e985e293f23813794315450d

www/.htaccess

@@ -185,6 +185,9 @@ redirect 301 /doc-contrib-guide/ui-text-guidelines /doc-contrib-guide/ux-ui-guid
 {%- endif %}
 {%- endfor %}
 
+# Redirect project contributor docs for stable series to latest
+redirectmatch 301 /([^/]+)/(?!latest)[^/]+/contributor(/.*)?$ /$1/latest/contributor$2
+
 # Redirect old cli-reference to the OSC latest docs
 {{ path_to_page('/cli-reference', '/python-openstackclient/latest/') }}
 

www/redirect-tests.txt

@@ -212,6 +212,11 @@
 {% endif -%}
 {%- endfor %}
 
+# Redirect project contributor docs for stable series to latest
+/nova/wallaby/contributor 301 /nova/latest/contributor
+/swift/xena/contributor/ 301 /swift/latest/contributor/
+/cinder/pike/contributor/foo.html 301 /cinder/latest/contributor/foo.html
+
 # Redirect old cli-reference to the OSC latest docs
 {{ path_to_page('/cli-reference', '/python-openstackclient/latest/') }}