Some project were tagged with newton-eol, but it seems later on
stable/newton was reopened and some generated patch merged.
This is a formal patch that corrects/adds the hashes of existing
newton-eol tags. (Note: the tags won't be recreated as the branch
is already marked as End of Life, this just sync the reported hashes
with the actual existing tags' hashes)
Change-Id: I7d03975ec2741817f4a2801e92672209c22f346a
This seems to be missing for requirements and the branch is still
visible at opendev [1]. (However 'git checkout stable/newton' gives
some error for me locally). Let's try to clean up this branch.
[1] https://opendev.org/openstack/requirements/commits/branch/stable/newton
Change-Id: Id7a52ccc244e52546d279dfac80b19ed0d68ef89
This transition the Newton branch and the Ocata branch to End of Life.
The last patch of these branch will be tagged with *-eol tag. Theese
branchs cannot be used anymore and will be deleted if this patch
merges.
This is needed as these branches are not actively maintained in
the recent period and thus gate is broken due to job failures.
By removing these branches, infra resources will be freed up, too.
Change-Id: I93822aa5fd9a1dde6b8226b4bc48adbc8093c28b
Some neutron related projects' newton and older branches seem to be
remained open accidentally, with this patch these branches will be
tagged with $series-eol tag and removed afterwards.
Change-Id: I7c100d84e22731710681e611fad6a70863ee2fb7
Fuel's newton branches seem to be remained open accidentally, with this
patch these branches will be tagged with newton-eol and removed
afterwards. fuel-upgrade's mitaka branch also added as it is also
remained open somehow.
Change-Id: I4a0561655fbe100139b10fa8a7f10eab0f5cc3e8
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
Use "edit-deliverable import-eol-tag" to record the information about
all of the existing newton-eol tags.
Change-Id: Iff29f42ccb02b9eec69750858e51459e33bc226f
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: Ia94eb26ccc9552193e9a21e5c771ce962721f6c9
This is a minor version bump because there is a database
schema migration in here related to a bug fix. It is optional
to actually run the schema migration, but the minor version
bump is used to signal it's more than just an ordinary
patch release.
Depends-On: I1aa3ca6cc70cef65d24dec1e7db9491c9b73f7ab
Change-Id: I0fd6f698b6bb240b8700a28abcd9e68d23f204ee
We found an issue with the packaging that caused some files to be
excluded in the released tarball. This release fixes that and includes
the current state of the module.
Change-Id: Ib87d85fca36263a2b4eece4fedc8fc8ea4d7153c
Please see the commit message of https://review.openstack.org/#/c/468925/
for the sad story on how we ended up bumping minor version on a stable
brunch. TL;DR the minimum requirements for one vendor was broken and
never worked in reality. Thus, the expected practical impact of the
version change is quite small.
Change-Id: I3e212741f8973b2aa95982a7fc9ebe6dcbc3d9dc
Előd Illés