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: I2b6482a78a7ddee2ee4466c4f6a24c1f8942c51a
The stable/liberty branch no longer exists, so we need to
remove it from the releasenotes
Depends-On: Ia4e01f00c4c5e9a2087df1e2a91d9154480a0422
Depends-On: I3bbe3bafa7ea3e627272103ac16a38f6a32a8a06
Change-Id: Ibafc01b24148d072dde636ad0cf6ee1d37c5609c
Closes-Bug: 1650033
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: I597e684dc1223e6292135c31e2abb56baf7e6249
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: Ib364dcc8eb31275a31c83b68d7914263b183e393
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
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.
also running job to treat warnings as errors.
Change-Id: I14a993f2830d3c0f9fd8d1bec7b2b71b315a13d2