OpenStack Networking (Neutron)
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Zuul 117e25345b Merge "Do not block connection between br-int and br-phys on startup" into stable/queens 1 year ago
..
_static Add reno for release notes management 6 years ago
_templates Add reno for release notes management 6 years ago
README.rst Do not use prelude section for individual release notes 4 years ago
conf.py Remove setting of version/release from releasenotes 4 years ago
index.rst Update reno for stable/pike 4 years ago
liberty.rst Add reno for release notes management 6 years ago
mitaka.rst Update reno for stable/mitaka 6 years ago
newton.rst Remove recursion from import_modules_recursively 5 years ago
ocata.rst Remove release notes from reverted patch 4 years ago
pike.rst releasenotes: Move Pike ignore-notes to a proper file 4 years ago
unreleased.rst releasenotes: Move Pike ignore-notes to a proper file 4 years ago

README.rst

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.