neutron/releasenotes/source
OpenStack Proposal Bot b81e05e44a Imported Translations from Zanata
For more information about this automatic import see:
https://docs.openstack.org/i18n/latest/reviewing-translation-import.html

Change-Id: Ib2fe1ebf00295ddd5f63d682ff713808c7fda102
2020-10-11 07:22:44 +00:00
..
_static Add reno for release notes management 2015-11-04 22:27:56 +00:00
_templates Add reno for release notes management 2015-11-04 22:27:56 +00:00
locale Imported Translations from Zanata 2020-10-11 07:22:44 +00:00
conf.py Switch to newer openstackdocstheme and reno versions 2020-05-20 22:06:45 +02:00
index.rst Update master for stable/victoria 2020-09-30 09:23:32 +00:00
liberty.rst reno: Remove remote names from branch specifiers 2018-02-22 15:39:47 +09:00
mitaka.rst reno: Remove remote names from branch specifiers 2018-02-22 15:39:47 +09:00
newton.rst reno: Remove remote names from branch specifiers 2018-02-22 15:39:47 +09:00
ocata.rst reno: Remove remote names from branch specifiers 2018-02-22 15:39:47 +09:00
pike.rst releasenotes: Move Pike ignore-notes to a proper file 2017-08-12 01:43:47 +09:00
queens.rst Update reno for stable/queens 2018-02-09 16:36:32 +00:00
README.rst Do not use prelude section for individual release notes 2017-08-04 07:17:52 +00:00
rocky.rst Update reno for stable/rocky 2018-08-09 21:54:37 +00:00
stein.rst Update master for stable/stein 2019-03-24 22:14:44 +00:00
train.rst Update master for stable/train 2019-09-26 09:44:13 +00:00
unreleased.rst releasenotes: Move Pike ignore-notes to a proper file 2017-08-12 01:43:47 +09:00
ussuri.rst Update master for stable/ussuri 2020-04-24 12:48:22 +00:00
victoria.rst Update master for stable/victoria 2020-09-30 09:23:32 +00:00

Neutron 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.