openstack
/
ovn-octavia-provider
Code Issues Proposed changes
ovn-octavia-provider/releasenotes/source
History
OpenStack Release Bot c2c87e6ff7 Update master for stable/victoria 
Add file to the reno documentation build to show release notes for
stable/victoria.

Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/victoria.

Change-Id: Icefb17a0b1dabb67d760ab6bfe44637fe3ea0236
Sem-Ver: feature
 		2020-09-24 16:24:19 +00:00
..
_static Initialize repository 2020-01-15 14:41:32 +00:00
_templates Initialize repository 2020-01-15 14:41:32 +00:00
README.rst Add release note README file 2020-04-24 14:07:27 -04:00
conf.py Switch to newer openstackdocstheme and reno versions 2020-06-09 18:05:08 +00:00
index.rst Update master for stable/victoria 2020-09-24 16:24:19 +00:00
unreleased.rst Initialize repository 2020-01-15 14:41:32 +00:00
ussuri.rst Update master for stable/ussuri 2020-04-11 18:46:45 +00:00
victoria.rst Update master for stable/victoria 2020-09-24 16:24:19 +00:00

README.rst

OVN Octavia Provider Release Notes Howto

Release notes are a new feature for documenting new features in OpenStack projects. Background on the process, tooling, and methodology is documented in a mailing list post by Doug Hellmann.

Writing release notes

For information on how to create release notes, please consult the reno documentation.

Please keep the following in your mind when you write release notes.

  • Avoid using "prelude" section for individual release notes. "prelude" section is for general comments about the release.
  • Use one entry per section (like "feature" or "upgrade"). All entries which belong to a same release will be merged and rendered, so there is less meaning to use multiple entries by a single topic.

Maintaining release notes

Warning

Avoid modifying an existing release note file even though it is related to your change. If you modify a release note file of a past release, the whole content will be shown in a latest release. The only allowed case is to update a release note in a same release.

If you need to update a release note of a past release, edit a corresponding release note file in a stable branch directly.