Commit Graph

12 Commits

Author SHA1 Message Date
Elod Illes 49dbf523ec [winstackers] 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: I58b9f2f8e073674ac61e8604e5b5473cacfbaf3d
2022-07-29 17:54:16 +02: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 47e9f159f8 [winstackers] 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: Ibccee22563d8cc0ed6e84eb35c1ee51f5090442c
2019-04-16 15:53:18 +10:00
Tony Breeds 49c4ce4110 [winstackers] 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: I6ed88d6e52f68cd15a73c0b8262d773e9aae1751
2019-04-16 15:53:12 +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
Claudiu Belu 280d46f9cf Release os-win 2.2.0 for Pike
Change-Id: Iaf5b1b08ec770f127e775c9591e7ce119572fbfc
2017-08-10 02:24:03 -07: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
Claudiu Belu 8bb48276de release os-win 2.1.0
Change-Id: Iee52d371a0ea5ee73ed646fc33504a47f785065e
2017-07-05 09:55:05 +00:00
Claudiu Belu cab712b870 release os-win 2.0.1
Change-Id: I3cc48f42513aa05da24280738fa0301ea8992df7
2017-04-20 03:53:24 -07:00
Claudiu Belu 7a9b5073df release os-win 2.0.0
Change-Id: I14ef9f709e7d32ef8b7861eb8b2aa470415e102f
2017-04-04 13:47:18 +00: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