openstack/kuryr-kubernetes
Code Issues Proposed changes
02329030a9
kuryr-kubernetes/releasenotes/source
History
Vu Cong Tuan 0bab16ac73 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: Ifb81fc7dd7dca02487b9e8d38d7b8de738ddeac5
2017-11-28 10:41:16 +07:00
..
_static Add Reno release notes support to Kuryr-Kubernetes 2017-11-23 15:26:59 +02:00
_templates Add Reno release notes support to Kuryr-Kubernetes 2017-11-23 15:26:59 +02:00
conf.py Remove setting of version/release from releasenotes 2017-11-28 10:41:16 +07:00
index.rst Add Reno release notes support to Kuryr-Kubernetes 2017-11-23 15:26:59 +02:00
README.rst Add Reno release notes support to Kuryr-Kubernetes 2017-11-23 15:26:59 +02:00
unreleased.rst Add Reno release notes support to Kuryr-Kubernetes 2017-11-23 15:26:59 +02:00

README.rst

Kuryr-Kubernetes 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.