Move the bulk of the instructions to a file that is part of the
documentation build so we can provide links to the HTML version.
Change-Id: I0aadc4034e68b0c6bf977248fdc075f10b7b0cc4
We need to document general guidelines for reviewing release requests.
This is following the recent gate breakage with oslo.utils 1.4.1.
The intent here is mostly for the special cases which impact stable branches,
but the semver reminder is important for non-stable branches also since
improper versioning on master where semver wasn't followed, e.g. incrementing
a patch version when the minor version should have been updated, has led to
a lot of the problems we see with stable branches.
Related-Bug: #1496650
Change-Id: I4c7013e265bb533dbac2c8804dea01dacff5de4b
the keywords 'project' and 'release' should be highlighted, since
they reflect the entries in yaml.
Change-Id: Ib6ba0d55daff85d63ba5a6f2ceb767eaf0c4473e