cinder/releasenotes
OpenStack Release Bot c0ff458b05 reno: Update master for Unmaintained branches
The stable/victoria and stable/wallaby branches have been deleted,
so reno can't find their release notes.  Use the victoria-eom and
wallaby-eom tags to indicate the end of the
Cinder project's maintenance of these series.

Also fix our override for the reno closed_branch_tag_re to include
the -eom tags. Add the changed reno.yaml file to all relevant
irrelevant-files lists.

This strategy is what we used for the yoga transition, and was
discussed at a cinder weekly meeting:
https://meetings.opendev.org/irclogs/%23openstack-meeting-alt/%23openstack-meeting-alt.2024-02-07.log.html#t2024-02-07T14:06:09

Change-Id: I505b7cc12888d2373a0550b40bb945d75bb11067
2024-03-13 12:56:42 +01:00
..
2017-07-25 14:24:18 -07:00

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.