Commit Graph

9 Commits

Author SHA1 Message Date
Elod Illes bcea38c28b [tacker] 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: Icc38f4ee117c1fc08f07a5c8a266c8f831c60014
2022-07-29 17:54:20 +02:00
Tony Breeds b2d318f7a8 [tacker] 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: I365587899fceb0bbbda27bd56d7b94e1bcdcc5fb
2019-04-18 09:09:05 +10:00
Tony Breeds f55a14cff3 [tacker] 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 since 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.

Don't tag python-tackerclient or tacker-horizon as they don't contain
any functional changes from already tagged and released versions.

Change-Id: Ife5dbd016149b3585ff0ecc41868d2564901668e
2019-04-18 09:07:23 +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
Sean McGinnis 3291999ef4 Add or update pike release notes links
Depends-on: https://review.openstack.org/540536
Change-Id: Ie42658df2aebd2563d693ff207abec5916cb1d52
2018-02-02 16:08:10 -06:00
gongysh 06fa94a573 bump tacker pike branch into 0.8.1 to include new backports
Change-Id: I64a125495e7e7474885d8263c63e20b0524cbc05
2018-01-16 11:24:24 +08:00
yong sheng gong d4eb791ce3 Get pike branch for tacker
Change-Id: Idcb3cb0c0f88a26474a55bbb19317d72074b5c49
2017-08-23 23:25:36 +08: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