Release notes are version independent, so remove version/release values.
We've found that most 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.
Change-Id: I9b631dbedd1b2c8bfe7430943dfc16e85b9f85e0
Do not specify a branch for unreleased.rst so it tests notes under
review rather than notes already merged.
Change-Id: If3e4982bcc457906eeebb99de660f6c594b122f0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The "unreleased" file being empty causes the releasenotes
job to fail with:
Warning, treated as error:
source/unreleased.rst:13:
WARNING: Inline interpreted text or phrase reference start-string
without end-string.
Change-Id: Ia5c2f2cf9ff37b5ec3f9e717a90b977d1e79b530
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: Ie5e108e73a33a8b2ff2e30f06d39afde1487e72f
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.
Change-Id: Ie1277428a3053d183df73bac882adc8aa0ac1079
