Commit Graph

9 Commits

Author SHA1 Message Date
Elod Illes 048c9235b0 [heat] 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: I6338e25979156cf69f6948863ddbce27b14cc105
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 88effc7577 [heat] 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: Ibba5629850762d515db87c828342a9b67e5ea08c
2019-04-16 15:53:17 +10:00
Tony Breeds fbc09d5b26 [heat] 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: Idfeb820aa24634ea68be8291af3a993f96a150ed
2019-04-16 15:53:07 +10: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 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
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
Bob.Haddleton 6290ac5bc4 Release tosca-parser 0.8.1
Change-Id: I944eca15c8e4346badf34ac454122c4e09452108
2017-04-22 11:25:10 -05:00
Bob.Haddleton 54e586c37f Add heat-translator and tosca-parser to openstack-releases
Historical release information is added to _independent and future releases
will use cycle-with-intermediary starting with pike.

tosca-parser 0.8.0 is released first and heat-translator will follow in
a future patchset

Change-Id: I5557685f1be1bafc0972648fdef873ee034dc4fa
2017-04-07 09:03:35 -05:00