Fix the sorting for EOL tags so when we collapse the release history
of a project to show it on the web site the sort works.
Also skip over the EOL tags when determining the "latest" release from
the branch. They are still displayed as part of the full tag history.
Change-Id: Iedde30f65bdfa89db0c6697ff031a75350090892
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add an API to Deliverable to let the sphinxext inject the series status
information, since the build conditions and working directory are
different under sphinx.
Change-Id: Id2bbdc4815564d28a5f4989bf7c74aed93e8c129
Story: #2001852
Task: #12620
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We still want to eventually change the release model name, but that's
going to be a little more complicated. In the mean time, change the
section title to reflect the fact that we expect only packaging and
deployment tools to use the cycle-trailing release model.
Change-Id: Ie7fcc06cbc9453c69caaef4bdd38edb3857f35c1
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Teams were being added in the order they were processed, which
could result in a jumbled list in the generated highlights page.
This sorts the teams by name to have some logical ordering to
the results to make it easier to locate specific team notes in
the output.
Change-Id: I91fef6e5e5aed71f285ba96d5458ad56568d1335
The original thought was to have this contain rich formatting
like used in reno. But the reality is, for what this is used
for, we really just want a bulleted list of highlights for
each project.
Based on the first couple of patches, this has been a point of
confusion for those trying to use this directive. This patch
simplifies things by just treating the cycle-highlights as a
list that gets added as bullet items to the generated results.
Change-Id: If265606eb20fa3d49e3cf4a684ea683de4267927
In order to help consumers of the cycle highlights data, this pulls in
some additional information about each team to have more of that info
in one easy to consume place.
Change-Id: Id45345999df5e204a8fa613676b3f27442551da7
Start with an empty string instead of None to avoid having all output
prefixed with "None".
Include additional debugging info, with some commented out for local
use later.
Change-Id: Ie09d740ad6bf0f396a26631e2db82801c043d248
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This adds the ability to provide release highlights in the deliverable
yaml file. These highlights can then be extracted and displayed into
published documentation using a new 'cycle-highlights' directive.
Change-Id: I40791dad4b5a4d2c4089e5e43d52f00b52cc3217
The validation job now requires type to be set, but we have several old
deliverables without it. Rather than edit all of them, set the default
to 'other' to avoid comparing None with a string.
Change-Id: I4e5a1d5f19dac8f6253bc7d6d040e1869c004d08
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We need a tool to verify that the release artifacts exist on the
tarballs site. The missing-releases command was already looking for
missing tags, so have it look for the tarballs, too.
This change refactors the URL generation code into a separate module so
it can be used by missing-releases and the sphinx extension. It also
creates a reusable function for testing a link, and has the gitutils
module functions responsible for looking for tags, branches, etc. use
it.
Change the default behavior to only look at the most recent release for
each deliverable, and add an option to go back to the previous behavior
of scanning all of them.
Change-Id: Ic7345466ccd83cf2d8d9d6d019107d6fbba171cc
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Since (and including) Ocata, Infra has been maintaining
a signing system for artifacts and publishing the
signatures:
http://docs.openstack.org/infra/system-config/signing.html
We should publish these signatures as part of the release
web site.
Change-Id: I06c099cdf9a2068f5d41f41f51176167374b577b
When we initialize a new series, we will have deliverable files without
any releases, yet. Ensure the validation, list-changes, and sphinx
extension code works in that case.
Change-Id: I724c2f77dac8c38e7145c00fc37a27d2078f9e69
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Update the sphinx extension to pull the release model and project type
from the local deliverable file instead of the governance repository.
Change-Id: Iddc1accc52fdcc6f0fad9993ec073de325f3a4b0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Show horizon plugins in their own section of series pages.
Change-Id: I145892f5e2e38fdac5f0fee40edbf0f037ff7a8e
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Teams add and remove repositories, change owners of repositories, and
are themselves removed over time. We can't rely on the current version
of the governance repository to include the information about who owned
a deliverable, so we need to put that information here in the releases
repository where we can track changes over time.
This patch adds support for a required "team" field to the deliverable
file, using the values set in previous patches in the series, and
updates the rendering code to use it instead of the project list from
the governance repository.
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Change-Id: I5941072c641c05bf0983984cae29a34927246d86
An earlier patch added sorting so we could support mixing releases
for independent projects. The sort change broke the pre-release
collapsing logic, so we were showing release candidates as newer than
final releases. This change fixes the sorting logic to ensure that
pre-releases come before finals by ensuring that we can always parse
the version string.
Change-Id: I3aa2e84c90ea05abe933bad0f32e902f39797b84
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Group the projects that trail the release cycle separately from the
other projects, rather than including them in the proper "type"
sections.
Change-Id: I97c209151a91ff5a18683c883ebca41c5386ff5c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We have been relying on folks adding entries to the deliverable files in
release order. That breaks the scripts that actually prepare the
releases, since those scripts only look at the last entry in each file
and releasing a stable version of an independent project often means
inserting an entry into the middle of the deliverable file.
This change tries to sort the versions in the deliverable files as it
reads them before building any tables. We use a tuple of the parts of
the version string, converted to integers where possible to avoid weird
alphabetical sorting of numbers and because SemanticVersion can't always
parse some of the legacy version tags project teams used.
The patch includes one change to an existing deliverable file to
demonstrate that the output is sorted properly.
Change-Id: I962a38db6ca79be02a3fdc8d387e30ee86a6a61c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Turn "_Independent" to "Independent" on the team pages.
Move the independent section on the main page above the team list to
make it easier to find.
Change-Id: I670643a791c7618a5c1febb7ec63e9540d4f206d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add pages to show the work each team has produced. For now, only
official teams using cycle-based release models are included. In a later
phase we will add deliverables that are currently listed as indepdent.
Change-Id: Ieb54aa7a4d2f58f462692e295c8f19978d5baa73
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Add support for multiple release notes links for deliverables composed
from multiple libraries.
Change-Id: I2f02028da456c96813eecbdbbb21307088c64476
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
The openstack-ansible project doesn't produce separate tarball
artifacts, so give them a way to turn off links that point to files that
don't exist.
Change-Id: I3fa5a053b61cd57e65222cde785ea7742870c8ee
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
When a final release is prepared, stop showing any preceding
pre-releases for that same version.
Change-Id: I0a73c72de1af5796f90deaaabbc2dbaba7abee32
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
For old releases, link to the wiki pages.
For liberty, link to the wiki and add links to the reno-generated
release notes pages that are available.
Change-Id: Iac5dbf2a64257d7457b136483322b2cb0d65fd1e
Show all of the release:independent projects release histories on a
separate page, now that they have moved out of the release series
directories.
Change-Id: I3fddbca590b1a8fcacc180a2730f0463dbcc0100
Deliverables which do not have any type were assumed to be
type:service deliverables and were listed with services,
resulting in a crowded and confusing output.
This patch makes sure they are listed in their own section.
It is still wrong for some of them (which should really have the
type:service tag), but less wrong than considering them all as
services.
Change-Id: I828b0fb245443cf5e3fb50c222da3f70c65a014b
Turn the version numbers in the tables into download links for
the tarball of a project at that version.
Change-Id: Id3fb9fbec75bc6b099589fd09a4cd4fafbc709e7
Include the earliest release and the most recent release in the summary
table at the top of each deliverable-type section.
Change-Id: Ib0704f4639bc6e350a9587aefba2819b65128940
Split the deliverables based on whether they are a service or
library. Default to service, since we do have some untagged projects and
they tend toward service rather than library.
Change-Id: Icaa2bacf5aadf7c53543c6c4a1abc5ef62eb77e7
