Commit Graph

13 Commits

Author SHA1 Message Date
Elod Illes 8dbc886084 [OpenStackSDK] Transition Pike to End of Life
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
2022-07-29 17:54:19 +02:00
Andreas Jaeger ebd0186899 Team OpenStackClient is merged into OpenStackSDK
Change Ib1088af1e56e083ee20e8b1623ec7d0fb4335334 merged the
OpenStackClient and OpenStackSDK teams into OpenStackSDK, follow this
for all deliverables.

Change-Id: I1ebf82909cb6c75519a7e1a004ae67a88dfb17f1
2020-03-27 11:21:42 +01:00
Sean McGinnis 1704aa624a
Raise YAML compliance to 1.2
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>
2019-07-31 09:34:38 -05:00
Tony Breeds ac580f5335 [OpenStackClient] create pike-em tag against final releases
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
2019-04-16 15:53:19 +10:00
Tony Breeds 55316981d9 [OpenStackClient] final releases for pike
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
2019-04-16 15:53:16 +10:00
Sean McGinnis 8df28d81d9 Remove per-release highlights for Pike
We've been warning that these are deprecated for awhile now, and
we now have enforcement in place to make sure no new highlights
are added.

We also have some automation that rewrites the deliverable files
but does not always do a great job, resulting in poorly formatted
text that causes warnings in the validation job.

Since many folks new to the release process, and some that have
done it for awhile, look at existing files to see what to do for
new releases, they do assume highlights should be used and end up
adding them to their deliverable file. Since most of these also
do not know to run local validatation, this results in gate
resources being used to just now be rejected with the current
checks.

To help prevent this from happening, and to get rid of the warning
messages from poor reformatting, this just removes highlights
from the last few releases.

Change-Id: Ie0b0e241c38f84bbc7b1ef5b09e97dc8ec466b39
2018-02-21 16:22:49 -05:00
Doug Hellmann 99b201ac88 add repo names to repository-settings for pike
Change-Id: I438a18e94b0de492d92587bca76ca0900c5534dc
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2018-02-07 18:21:37 -05:00
Doug Hellmann c085ac7568 add release-notes URLs for some pike deliverables
Update the deliverable files that have pike release notes
already. Some of the changes are normalization from rewriting the
files. The only differences should be the order of items and the value
of the 'release-notes' key.

Change-Id: I9bd7ec180eee007d80297735688e7702a137153f
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-08-01 10:29:04 -04:00
Doug Hellmann dfdb54e10b create stable/pike branches for all of our libraries
Except barbicanclient which is working on a critical fix and
neutronclient which had a late release request that we haven't
resolved.

Change-Id: Ib4866823c7f3477e09999106086a882d8f650b64
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-07-28 16:02:51 -04:00
Dean Troyer 3347a99b5c Release os-client-config 1.28.0
Change-Id: Iaf8534d46c4fced5a16ecb3c4dbae0c7e8ecb9ee
2017-07-06 20:46:46 -05:00
Doug Hellmann a7f22abb10 remove send-announcements-to from pike projects
We no longer use the send-announcements-to field for anything.

Change-Id: Iec0b11ced00ea06ac459ad544b1cb2db20d2892d
Signed-off-by: Doug Hellmann <doug@doughellmann.com>
2017-06-06 16:01:06 -04:00
Dean Troyer 042e9f39a2 Release os-client-config 1.27.0
Change-Id: Ie24eb3699fedd8d2a38e37ae00c3e58000f44b2d
2017-04-26 09:50:54 -05:00
Doug Hellmann 8d5d768876 create stub files for pike deliverables
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>
2017-02-22 08:54:18 -05:00