As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: Ib7f583f526db7a33193f77efc39fc61bd7382196
... the ultimate. really. this time.
openstack-ansible-ops repo could not be tagged as the tag-releases job
calls 'git submodule [..]' command at a point, but that failed as there
is no .gitmodules added. A workaround is now merged that removes the
cached submodule, so let's tag openstack-ansible-ops repo now for real.
Change-Id: Ib29ddc8a3f9ed20c048bb3f254632438d781e69a
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: I1ac3e000f74a97d1b0758569a92e3f2d7e396427
The original stein-eol patch of OSA roles [1] missed 2 role repos.
This patch adds that.
Note that however openstack-ansible-ops was added (with the correct
hash) it was skipped during the EOL'ing due to unknown reason.
[1] I56f3bd28f1f1dddd31da166db44615707ba1e255
Change-Id: I14ab6ac024d791047e386dc683a696c98e9a9de2
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: I7a29f0e70a96296fb0d285f41672e832cb1d94b7
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: I5deb2c0958fd0d49d32de93503a886af8ba3e429
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: I31fc63ceb1e7b6fce300916561ce72d17cb6ec15
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: Idd5a96156aa933c0edcc81c1b582ea5e04f8aff0
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: Ibb50fe08f0766b4cf61308355032b6dc0f6e69e8
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: I5fc5e039d0910bf3f3362c78c0a9f5c968ac5509
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: I527565731d2632bae59c0283791be0c63876ea24
As announced on mailing list [1], this patch transitions the Stein
branch to End of Life. The last patch of the branch will be tagged with
stein-eol tag. stable/stein branch cannot be used anymore and will be
deleted if this patch merges.
This is needed as stable/stein is not actively maintained in recent
period, 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/stein is deleted. 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.
[1] https://lists.openstack.org/pipermail/openstack-discuss/2023-September/034965.html
Change-Id: I63afa8e9c6deaf78fea679d9dbd65c14ddaa249e