Fix the way the error message is constructed when there is a bad SHA to
the error is reported instead of seeing a KeyError.
Change-Id: I5ff521dee807d3497b2d3496f4361c8fad57d86e
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
When new repositories are added to a deliverable, we want to recognize
them as new and show all of the changes. The existing logic using the
generator expression fails with a StopIteration exception when there is
no repository matching the new version in the previous version.
Change-Id: Ifb426b89c85b21b18208a630fa5187a279e6ce2f
If there are multiple deliverables (like in neutron), we should make
sure we extract git hash for corresponding repo to extract diff between
previous and proposed versions.
Change-Id: I0e1210c8582ef87c099e45058b415a6e2346ed48
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
Add git diff output for requirements related files to show what
requirements actually changed over the span of the release, if any.
Change-Id: Id87c858897e75ddcee2150912d3e087743554585
Include the graph log output for the range merging in so we can try to
verify that there are no merges from a bad branch.
Include the full log output for the commits so it is easier to tell
which ones might be features.
Change-Id: I74e34ce78abef63a38b41d6ff1d2d275317fb209
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
The git describe command reports errors if there are no tags to be used
to get a description. Trap the errors in places where it is reasonable
to encounter that situation.
Change-Id: I436af248b1740c493b14178cbbe59c8b0474aa94
- Add missing entries for Austin to Cactus
- Remove development milestones, alphas and temporary artifacts
- Remove projects that were not officially part of OpenStack
by the time of each release
- Remove extraneous entries (like neutron-*aas before kilo)
- Reorder some releases (0.10>0.2)
- Remove oslo-incubator where it was mentioned, since it's not
really released
- Fix validation code to handle just-deleted files
Change-Id: Ia9fd26cbefe9c25c9fecab33069b2826e2328675
start_range should be just the hash. previous_release
contains the full information about the release, we just
need to pick up the hash from it
Change-Id: Idb0d79f72c7d3f0d19fa40567bc03b51062872df
If we can't figure out the previous version from looking in the YAML
file, use git describe to find it.
Show the version number being released in the header of the list-changes
output so we can verify that it matches the expected value after seeing
what sorts of changes are included.
Change-Id: I8f65400900ee0779fd8d1736bf319e638ebbeca0
Have each subprocess call change its working directory instead of
shifting the working dir for the entire process.
Change-Id: Ia1ada14bac7bc6b3b006c1ef8930192761111877
Look for the SHA being assigned a new version in the descendants of the
previous version to ensure it is merged properly.
Change-Id: I82fcb9295bc5eea0c404db898272329dcc515b7b
Sometimes we want to release something that isn't HEAD, so include the
unreleased changes in the output report.
Change-Id: I7265e892dff48a2c0a618f6d3b2a9ceff6e095bf
Let sha_for_tag assume that the repository already exists, and create a
clone_repo function to be used to enforce that.
Change-Id: Iab9b54cf7a82b70aeebc46a09cab92ccfbe76f4c
Update the validate command to compare the actual SHA of a tag with the
one in the file to ensure they match.
Change-Id: I5c04667cbb43cda548c3cc05a47d5a5830b32951
The merge commits created by zuul do not always list all of the files
being modified, so use git diff instead of git show.
Also force python to use unbuffered I/O so the output comes out in a
useful order instead of mixed up with the subprocess commands.
Change-Id: I5e0e4602e463c05e488537192be8ba59c08644dc
Move some of the validation code into a real python package so we can
more easily reuse it.
Make the validation script reprint all errors, for cases where it has
checked a lot of files and the original messages might have been mixed
in with other output.
Fix the launchpad project name for tooz so the validation script will
pass.
Change-Id: I17534d460dd9ed19d10e48a0ef5d28dac3ab0fe7