Change Ib1088af1e56e083ee20e8b1623ec7d0fb4335334 merged the
OpenStackClient and OpenStackSDK teams into OpenStackSDK, follow this
for all deliverables.
Change-Id: I1ebf82909cb6c75519a7e1a004ae67a88dfb17f1
The YAML 1.2 spec was released in 2009. It's probably been enough time
that it's safe to move to it.
The only issue for out YAML usage was 1.2 dropped the use of Yes, No, On,
and Off as valid boolean values.
Change-Id: I608e09d219379e00cca15c5ff165bb63aecfe9f2
Signed-off-by: Sean McGinnis <sean.mcginnis@gmail.com>
We have static URLs redirecting /constraints/upper/series to the
appropriate git interface. In the next change in this series we move to
a data-driven model so let's supply the data :)
Even though we have tag history that goes back to Folsom only import
Juno and later because that's when we first added constraints support
This means as the create and delete branches for requirements, like
other projects, we have a central source of truth (other than git) from
which to update the htaccess redirects.
I had update deliverables.py to account for the fact most of the
requirements branches don't have a release. This does make the table
look a little funny (as the earliest release is the series eol tag :()
but I'm not sure how we can do better there.
Change-Id: Ie8e60dc865ab301539c0bb085a52dd25f3f62edf
Add an extra check that there are no notes links for repos not related
to the deliverable.
Change-Id: I7f0fb614cff8ae38c907670da484c3c75599c7c0
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
We've deprecated per-release highlights and are now removing them.
We also now require repository-settings for deliverables. This adds
the one and removes the other.
Change-Id: I7fb0ad93a12c7da89c9f6af70b03b347e1331242
We no longer use the send-announcements-to field for anything.
Change-Id: I605b86261e13e13f017264992090c5f726e3e605
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Some deliverables used to follow a -with-milestones model
(with aligned release versioning) before they switched to
-with-intermediary. This commit fixes that history.
Change-Id: I400e06024d41ed74b7a05544dcd97083a96a111d
Depends-On: Ifd695164e3a554388a8818e37d43283a5cd6a44e
The governance repo has the team name as "OpenStackClient" so use that
form everywhere in the releases repo.
Change-Id: I58a623d19a5f4fc382faeea25b2561ec5fe034a4
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
updating these old files also requires fixing them to pass the modern
validation tests
Change-Id: I135d37be6c35603b6929140eb756ceab3db65945
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This release will contain 5d276b677c62b5d7a9a660d273209e76b154d503 which
is a g-r sync for stable/juno which is needed to unwedge Horizon on
stable/juno:
Ic7516b79ed1eea1330f008ce83c8727fd974bdd3
We've already isolated the 0.14.x series in Juno g-r from the 0.15.x
series in Kilo g-r here:
I3f9d3fe4c5688685fb9afe1762b698c4f86a4a68
So only Juno should get the 0.14.3 release in the CI jobs since Kilo g-r
requires:
python-glanceclient>=0.15.0,<0.18.0
Also adds the 0.14.2 release to the Juno deliverable yaml for completeness.
Change-Id: I7747574bfcf9cc77073840d1cd4af80b2567dca9
This contains the g-r sync for stable/juno so that oslo.utils is
capped in python-ceilometerclient.
Note that we can't release this until global-requirements on
stable/kilo are adjusted so kilo doesn't pick up the 1.0.15 version.
Depends-On: I81409216c895fbf640bb0e9f3d772f09cd7052ca
Change-Id: I28d1b319cf5fe36c64e7b9f8a8ced67b072f660a
Closes-Bug: #1494516
A relase of oslotest with all requirements capped as per stable/juno
global-requirements is needed.
Change-Id: I62c43aaa21e55f8a7fd0cd43783ab94a3b3f234d
Closes-Bug: 1488752
The stable/juno branch for oslo.utils was created from the 1.4.0 tag.
Release 1.4.1 which just includes a g-r sync. This will unblock
ceilometerclient in stable/juno
Change-Id: Ibc5cc60848c45f92d09968395bc13f0ce6e816f1
Closes-Bug: 1488746
The pycadf gate is failing becase oslo.messaging 1.4.0 has uncapped
dependancies (specifically oslo.utils). The current stable/juno
branch has the correct caps. Lets release that as 1.4.2
Not 1.4.1 was tagged sometime ago but isn't in this repo
Change-Id: I062b6ce1b3dc83f37ef3391e28a656aa1514af37
Closes-Bug: 1488737
Commit c213ffda17d09a68fdbb619ba6db4b8a101e85a9 synced
python-swiftclient with global-requirements from stable/juno to cap
futures so it doesn't conflict with taskflow (which has futures capped
on in juno per g-r).
Requirements commit f7c3edbc9fa40e6a3979a2dc58c2a9a6af374607 raised the
cap on python-swiftclient in global-requirements to <2.4.0 so this 2.3.2
release will fix the futures dependency conflict.
This change includes the hashes for 2.2.0->2.3.1 since those are the
other possible versions in the supported range for g-r on stable/juno.
Closes-Bug: #1486576
Change-Id: Ib7c987d2eaf46dc18b166d773b8125b834ee5c70
- 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
Commit 66c9ae4521f3abacd3df1403e40b639bb2d58679 caps networkx so that
gate-cinder-python26 jobs will work in stable/juno again.
g-r for stable/juno: taskflow>=0.4,<0.7.0
Closes-Bug: #1484267
Change-Id: Icfa63afb67e6e131b962783936840b1ddf315e9e
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
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 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
Andreas Jaeger