[TripleO] stable/wallaby branching
Hello TripleO,
quick update on the plan for stable/wallaby branching. The goal is to release tripleo stable/wallaby just after PTG i.e. last week of April.
The tripleo-ci team have spent the previous sprint preparing and we now have the integration and component pipelines in place [1][2]. As of today we should also have the upstream check/gate multinode branchful jobs. We are planning to use this current sprint to resolve issues and ensure we have the CI coverage in place so we can safely release all the tripleo things.
As we usually do, we are going to first branch python-tripleoclient and tripleo-common so we can exercise and sanity check the CI jobs. The stable/wallaby for client and common will appear after we merge [3].
*** PLEASE AVOID *** posting patches to stable/wallaby python-tripleoclient or tripleo-common until the CI team has completed our testing. Basically until we are ready to create a stable/wallaby for all the tripleo things (which will be announced in due course).
Obviously as always please speak up if you disagree with any of the above or if something doesn't make sense or if you have any concerns about the proposed timings
regards, marios
[1] https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-integr... [2] https://review.rdoproject.org/zuul/builds?pipeline=openstack-component-tripl... [3] https://review.opendev.org/c/openstack/releases/+/785670
On Fri, Apr 9, 2021 at 7:02 PM Marios Andreou marios@redhat.com wrote:
Hello TripleO,
quick update on the plan for stable/wallaby branching. The goal is to release tripleo stable/wallaby just after PTG i.e. last week of April.
The tripleo-ci team have spent the previous sprint preparing and we now have the integration and component pipelines in place [1][2]. As of today we should also have the upstream check/gate multinode branchful jobs. We are planning to use this current sprint to resolve issues and ensure we have the CI coverage in place so we can safely release all the tripleo things.
As we usually do, we are going to first branch python-tripleoclient and tripleo-common so we can exercise and sanity check the CI jobs. The stable/wallaby for client and common will appear after we merge [3].
*** PLEASE AVOID *** posting patches to stable/wallaby python-tripleoclient or tripleo-common until the CI team has completed our testing. Basically until we are ready to create a stable/wallaby for all the tripleo things (which will be announced in due course).
update on this at http://lists.openstack.org/pipermail/openstack-discuss/2021-May/022276.html
Obviously as always please speak up if you disagree with any of the above or if something doesn't make sense or if you have any concerns about the proposed timings
regards, marios
[1] https://review.rdoproject.org/zuul/builds?pipeline=openstack-periodic-integr... [2] https://review.rdoproject.org/zuul/builds?pipeline=openstack-component-tripl... [3] https://review.opendev.org/c/openstack/releases/+/785670
participants (1)
-
Marios Andreou