OpenStack Release Bot eda2def050 Update master for stable/2023.2
Add file to the reno documentation build to show release notes for

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

Sem-Ver: feature
Change-Id: I5acf5babe7f81123d3b883ae91e75ae86e198d92
2023-09-15 14:06:01 +00:00
_static Initialize repository 2020-01-15 14:41:32 +00:00
_templates Initialize repository 2020-01-15 14:41:32 +00:00
2023.1.rst Update master for stable/2023.1 2023-03-02 11:45:46 +00:00
2023.2.rst Update master for stable/2023.2 2023-09-15 14:06:01 +00:00
README.rst Add release note README file 2020-04-24 14:07:27 -04:00
conf.py remove unicode from code 2021-12-24 14:46:25 +08:00
index.rst Update master for stable/2023.2 2023-09-15 14:06:01 +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
wallaby.rst Update master for stable/wallaby 2021-03-30 18:28:22 +00:00
xena.rst Update master for stable/xena 2021-11-08 11:36:38 +00:00
yoga.rst Update master for stable/yoga 2022-03-10 12:13:45 +00:00
zed.rst Update master for stable/zed 2022-09-16 14:40:14 +00:00


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


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.