openstack/neutron-tempest-plugin
Code Issues Proposed changes
master
neutron-tempest-plugin/releasenotes/source
History
LiZekun 8ad510e60b Remove unicode literal from code 
All strings are considered as unicode literal string from Python 3.

This patch drops the explicit unicode literal (u'...')
appearances from the unicode strings.

Change-Id: I71621b95c87e7c10e86d8341173967235912053d
2022-06-06 11:37:59 +00:00
..
_static Apply cookiecutter to newly split project 2017-09-07 22:23:55 +05:30
_templates Apply cookiecutter to newly split project 2017-09-07 22:23:55 +05:30
conf.py Remove unicode literal from code 2022-06-06 11:37:59 +00:00
index.rst Sync Sphinx requirement 2019-06-19 22:58:47 +08:00
README.rst Add release notes job to zuul template 2018-09-13 15:26:04 -06:00
unreleased.rst Apply cookiecutter to newly split project 2017-09-07 22:23:55 +05:30

README.rst

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