This transition the Pike branch to End of Life. The last patch of the
branch will be tagged with pike-eol tag. The stable/pike branch cannot
be used anymore and will be deleted if this patch merges.
This is needed as stable/pike is not actively maintained in the recent
period and thus gates are mostly broken due to job failures. Besides,
by removing these branches, infra resources will be freed up, too.
Please try to identify any zuul job, that is defined outside of the
repositories in this patch (for example in openstack-zuul-jobs, etc.)
and won't be used anymore if stable/pike is deleted, and propose a job
removal patch for them.
Please +1 if the team is ready for us to proceed with this transition,
or -1 if there are still some activity on the branch and the team wants
to continue to maintain it.
Change-Id: I19ca4446042cae5179c545ab6d6de395da804d8e
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>
This is a procedural review to transition pike into extended maintenance by
creating the pike-em tag
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: I3b334b461590c74c4eda22a28af54b5b24fd1e66
This is a procedural review to tag a final release for each deliverables ; and
It's possible that the release isn't needed (for example if there are no code
changes sine the previous release, sadly that's non-trivial to detect en masse.
If you are the PTL or release liaison for this team please +1 this review
if it is ready or -1 and take over the review to correct mistakes.
Change-Id: Id510eb5767775defdb903c5f7ecc887361699a04
Contains fixes for the following bugs:
- Remove hard-coded policy choices for creating a server group (bug 1732938)
- Neutron agent delete: remove the wrong argument (bug 1711301)
- Fix 'project purge' deletes ALL images problem (bug 1717130)
Change-Id: I90ab098efb1b39b834aa55c8f27f99453da6d311
Following the release process[1], all projects that are publishing
release notes have the notes link included in their deliverable
file.
Extra changes (like true -> yes) are included due to the use of
edit-deliverables YAML linter.
Change-Id: Ibd63f0f8bf1d406039c0196560768beb9f6650ce
We no longer use the send-announcements-to field for anything.
Change-Id: Iec0b11ced00ea06ac459ad544b1cb2db20d2892d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
This is a bug-fix only release to correc an issue that broke the
Ironic CI. The minor bump is due to a global-requirements bump
that was also merged immediately after the 3.10.0 release. We'll
not do that again...
Change-Id: I3ea9d1028e9187b29ad414affc0d47c79f8f3e3e
A patch between 3.9.0 has a fix where get_one_cloud is only called with
validate=True for auth_required=True commands.
Without this patch [1], deploying os-client-config 1.27.0 will fail to
call keystoneauth library.
[1] 1c3cb0a3b54cdb6cd5b27e88372b65cfac844422
Related-Bug: #1687706
Change-Id: I482ead44d81c5d2ff32c2c23447440edac67a5ad
Create the deliverable files for Pike based on the ones that were
released during Ocata. Leave out release and branch information, since
that will be filled in for the first release.
Change-Id: Idf3e9a3eadba86038f6b69527a109a0cad79bf8c
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
Elod Illes