5 Commits

Author SHA1 Message Date
Akihiro Motoki
010b133938 Do not use prelude section for individual release notes
prelude section is prepared for general comments about a release [1].
At now neutron release notes use prelude section randomly.
Some rel notes use it and some do not.

This commit drop or move prelude section in Pike release notes.

In addition, some guideline on writing a release note
to the release notes howto page.

Change-Id: I53fefcc3eed30700d095c77d9e000319668097e8
2017-08-04 07:17:52 +00:00
Akihiro Motoki
6f1ecf2466 Exclude relnote from past releases from Pike relnotes
reno includes release notes touched in a target release
even if they are added from past releases.
The recent release note cleanup I made as part of doc8 adoption
and some other cleanup touched release notes from past releases.
As a result, we see several number of release notes from past
release in the Pike release notes unexpectedly.

Also adds a warning note to the release notes howto page

Change-Id: I127f96896488e9992d9309d76055b4883f6a62f3
Closes-Bug: #1708560
2017-08-04 07:16:57 +00:00
Akihiro Motoki
d3c393ff6b Update the documentation link for doc migration
* Update the URLs affected by the doc-migration
  (/developer/<project>/ to <project>/latest/)
* Follow content rearrangement
* Convert links to local documents into :doc: or :ref:
* Use https instead of http for the updated links on docs.openstack.org.

Part of the doc-migration work.

Change-Id: I62e317d9198f175a43d73bbfd419b6878de90d5a
2017-07-22 18:46:13 +09:00
Prince Nana
c1540459b4 Correcting a spelling in README
Change-Id: I08b770559ae69060ea4ec5aabce8d2d6d36c83cc
2016-10-24 17:19:49 +00:00
Sean M. Collins
24bfc35d3e Add README with links on how to create release notes
Change-Id: I7944d4ad8d53418d36a2cf894fd9120c672521bf
2016-01-09 16:31:55 -08:00