Add file to the reno documentation build to show release notes for
stable/train.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/train.
Change-Id: Id476cf89f4f8f0ab41529d44510a7ed0572c63c5
Sem-Ver: feature
Add file to the reno documentation build to show release notes for
stable/stein.
Use pbr instruction to increment the minor version number
automatically so that master versions are higher than the versions on
stable/stein.
Change-Id: I56674b093e7de39399d7753df7f9cd46ccd197e5
Sem-Ver: feature
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: I63745a207ba9123b34d2323d00b22e8cbdd253dd
This should have been deleted in change
Ic373a0ab62c610fae1cbdaf489ba27e9cf02ba5b, but remained due to change
Id69951958d9d74e51c1cab9b992d286c8e852713
Change-Id: I47327866921be879967e90f1f8d965d59c9bf5d5
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
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
* 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
* Switch the release note theme to openstackdocstheme.
* Use the new style of setting of openstackdocstheme
of the in-tree documentation.
Change-Id: I0424f097c0f5d78a539bc997e2cd61119d606524
Basically, the commit removes the file encoding - since jenkins is fine
with it, means it was really unnecessary and the change makes sense.
Change-Id: Id0821c9b11b9efad1836596c407566c9eb4dc11a
Releasenote translation publishing is being prepared. 'locale_dirs'
needs to be defined in conf.py to generate translated version of the
release notes.
Note that this repository might not get translated release notes - or
no translations at all - but we add the entry here nevertheless to
prepare for it.
Change-Id: Ic0d37f26c59aeed3a55a5b229404c1d18bf248f0
In order to support automatically updating the release notes when
we create stable branches, we want the pages to be in a standard
order. This patch updates the order to be reverse chronological,
so the most recent notes appear at the top.
Change-Id: Iddc12f8c0bef847d3b3a45c05fedcb64bb2be2a1
The title is not valid RST, remove the extra "+" and align the headings
with the length of the string.
Change-Id: I32afdcc84e51a53a63a7cacaeba271b2f7811d75
We need a release notes page to show notes for unreleased versions by
scanning the "current" branch. This ensures that notes files cannot be
merged if they break the releasenotes job.
Change-Id: Ic0614c37a67ebd28d1da0c0947c69c753833c870
Signed-off-by: Kyle Mestery <mestery@mestery.com>