openstack
/
dragonflow
Code Issues Proposed changes
dragonflow/releasenotes/source
History
rajat29 954a56aa3d Remove setting of version/release from releasenotes 
Release notes are version independent, so remove version/release
values. We've found that projects now require the service package
to be installed in order to build release notes, and this is entirely
due to the current convention of pulling in the version information.

Release notes should not need installation in order to build, so this
unnecessary version setting needs to be removed.

This is needed for new release notes publishing, see
I56909152975f731a9d2c21b2825b972195e48ee8 and the discussion starting
at
http://lists.openstack.org/pipermail/openstack-dev/2017-November/124480.html

Change-Id: I5b002aafe05541dfbfc81298446079fe46f80ccd
 		2017-11-17 10:23:38 +05:30
..
_static Support reno releasenotes 2017-02-09 13:41:21 +08:00
_templates Support reno releasenotes 2017-02-09 13:41:21 +08:00
README.rst Update and optimize documentation links 2017-07-19 10:58:45 +00:00
conf.py Remove setting of version/release from releasenotes 2017-11-17 10:23:38 +05:30
index.rst Update reno for stable/newton 2017-10-26 18:54:28 +00:00
mitaka.rst Support reno releasenotes 2017-02-09 13:41:21 +08:00
newton.rst Update reno for stable/newton 2017-10-26 18:54:28 +00:00
ocata.rst Update reno for new releases 2017-02-13 17:23:38 +08:00
pike.rst Fix new release note in releasenotes 2017-10-13 16:53:27 +08:00
unreleased.rst Support reno releasenotes 2017-02-09 13:41:21 +08:00

README.rst

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

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