Commit Graph

10 Commits

Author SHA1 Message Date
Elod Illes 4a374066a9 [ironic] 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: Icb8d042aeaf5e83cab587ff3f60af6b0f2c275b6
2022-07-29 17:54:16 +02:00
Tony Breeds 29898a5151 [ironic] 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: I065d261cc6f1294d7b344800d75d5aa718fefd02
2019-04-17 12:27:34 +10:00
Mark Goddard 0dc196048f Release bifrost stable branches
Creates the following releases of the bifrost project:

* 4.0.2 (pike)
* 5.0.3 (queens)
* 5.1.4 (rocky)
* 6.0.1 (stein)

Change-Id: I627ad971b3ddac6b4556525066633bd4190177e0
2019-04-15 14:57:20 +01:00
Zuul ee4a17c404 Merge "Release bifrost 4.0.1 for Pike" 2018-02-09 02:53:40 +00:00
Dmitry Tantsur 6bce944c18 Release bifrost 4.0.1 for Pike
Change-Id: Ifd4e76cd366a98f8d1e67861c2d54d5a8227b9db
2018-02-08 09:33:50 +01: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
Thierry Carrez 175eb304c5 Add Pike release notes links
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
2017-08-18 10:13:11 +02:00
Julia Kreger c2df11f6ef Release bifrost 4.0.0 for pike
Change-Id: I3e23311ecaf74ea950965a3824b13016bb6371e8
2017-08-14 13:41:50 +00: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
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