Commit Graph

11 Commits

Author SHA1 Message Date
Elod Illes 336339abe3 [vitrage] 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: Ia479a56af1e47da76f2bb92ce4bb245e9db4a316
2022-07-29 17:54:21 +02:00
Tony Breeds e4275eba26 [vitrage] 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: If990bb9d1fe180ecdc44b63aa7f982fd446f7497
2019-04-16 15:53:19 +10:00
Tony Breeds 703166665c [vitrage] 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: I3a3e3a51992f9171e5fa874c11f40c7ffedda4b3
2019-04-16 15:53:14 +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
Idan Hefetz ddc7f81b5a Release vitrage and vitrage-dashboard
Change-Id: I60ccbc8ddf3ec32a94594df2f41a5a47f47adde4
2017-08-21 18:21:52 +00: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
Ifat Afek 4cd1dfa125 Create stable/pike branches for vitrage and vitrage-dashboard
Change-Id: Id9018d99cb6215b104ab1ec31385759e46457890
2017-08-09 15:23:47 +00:00
Ifat Afek 7313817955 Release vitrage, python-vitrageclient and vitrage-dashboard
Change-Id: Ic90ca3f3529f71d289cd774ff4616cc379f8ee51
2017-07-27 14:41:14 +00:00
Ifat Afek dc5e52f746 Release the vitrage deliverables
Change-Id: Id7ef6b61f4a06ab01d1db7065ed1c1215290021d
2017-06-08 09:52:40 +03: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