The documentation tools did not have launchpad projects from which we
could import the version numbers in the appropriate series, so
approximate that by comparing the dates of the tags to the end date of
the release cycles.
Change-Id: Ibbca82ff37dffab7b93b91104cba783cc7073a6d
Be more explicit about how we check for a SHA, instead of just checking
a few commonly used names.
Change-Id: I3878159f45d40bb0291a8352c0e6485a84a165e0
If we submit changes to the validation script we want them tested
against something, so default to looking at all of the files for the
current release. Running it against all files for historical releases
would take a long time and might fail if we introduce schema changes to
the deliverables files.
Change-Id: If9b840403f52abde597e1d99b594be338c42aa3d
Fix the import script to ignore some projects that don't have their own
launchpad pages, yet, and to use the right names for pages where they
don't match the git repositories.
Add history for a few missing projects that can be imported after the
changes mentioned above.
Change-Id: I1f22c8cfcd66a02e3c5e1e5076fcdada42178948
Add a basic validation tool to check the input values against the
current state of the repository.
Change-Id: I570c7028e4dc469a670ff933fdfe6bde3095d0ac
Add deliverable files for existing releases, including the script used
to generate them from launchpad and git data. This data is known to be
incomplete, and is meant as a starting point for reconstructing the full
history.
The output from running the script [1] shows that many projects we
expected to treat as deliverables do not yet have a launchpad page.
[1] http://paste.openstack.org/show/336176
Change-Id: I1a64c8b6b99ec575c00c1ebad93a5f6dc70c9718
