48170e028c
Stable branches for rocky to ocata are in extended maintenance. As such, they do not get frequent updates to the release notes. Building the release notes can take quite awhile, especially in the gate where it build them repeatedly in one job for each translation that is available. Each stable branch using the reno sphinx extension directive needs to scan the git history and dynamically generate the RST used for the series release notes. To speed up how long this takes, this patch makes these closed series' release note pages static so this expensive operation doesn't need to be performed for release notes that are not changing. If we do backport a patch to one of the Extended Maintenance branches we can manually refresh the the static release notes using the instructions in the previous patch's README. Change-Id: I742929ade3dd8a87dd03e86f8b4f22a0f61ef30e Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
Release notes
The release notes for a patch should be included in the patch. The intended audience for release notes include deployers, administrators and end-users.
A release note is required if the patch has upgrade or API impact. It is also required if the patch adds a feature or fixes a long-standing or security bug.
Please see https://docs.openstack.org/cinder/latest/contributor/releasenotes.html for more details.