channels/*-4.3: Promote 4.2.28 and 4.2.29 to fast/stable regardless of arch #302
Conversation
openshift-ci-robot
added
the
approved
|
@wking: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
The decision to go muti-arch #229 was done later i.e. after we merged x86_64 specific edges to fast and stable. ART need to send 3 PRs (i.e. candidate, fast and stable) at one go. So that we will not put our-self in this position again. |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
openshift-ci-robot
added
the
lifecycle/stale
|
Stale issues rot after 30d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle rotten |
openshift-ci-robot
added
lifecycle/rotten
|
Rotten issues close after 30d of inactivity. Reopen the issue by commenting /close |
|
@openshift-bot: Closed this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/reopen |
|
@wking: Reopened this PR. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
openshift-ci-robot
added
the
needs-rebase
…f arch They went into candidate without architecture qualifiers in 0157b7b (Merge pull request openshift#229 from sosiouxme/patch-5, 2020-05-08) with an explicit decision to go multi-arch in db17a23 (candidate-4.3: allow multi-arch 4.2 s390x upgrades, 2020-05-05, openshift#229). But for some reason had arch guards when they went into fast with cb27d43 (Add 4.2.28 to fast, 2020-04-08, openshift#162) and 9d10713 (Add 4.2.29 to fast, 2020-04-15, openshift#178) and stable with 74b433b (Add 4.2.28 to stable, 2020-04-08, openshift#163) f652963 (Add 4.2.29 to stable, 2020-04-15, openshift#179).
wking
force-pushed
the
arch-agnostic-4.2.28-to-fast-4.3
branch
from
10b2c24 to
6b94854
Compare
openshift-ci-robot
removed
the
needs-rebase
|
Rebased onto master with 10b2c24 -> 6b94854 to address: $ hack/stabilization-changes.py
INFO: considering promotions from candidate-4.3 to fast-4.3 after P1W
INFO: recommended: 4.2.28 (142 days, 7:30:27.122771)
DEBUG: channels/fast-4.3: Promote 4.2.28 to fast-4.3
DEBUG: It was promoted the feeder candidate-4.3 by 0d960959e4 (Merge pull request #526 from sdodson/backfill-stable-previous-minors, 2020-11-09).
INFO: recommended: 4.2.29 (327 days, 3:26:31.122771)
DEBUG: channels/fast-4.3: Promote 4.2.29 to fast-4.3
DEBUG: It was promoted the feeder candidate-4.3 by 0157b7b6e2 (Merge pull request #229 from sosiouxme/patch-5, 2020-05-08).
...for #75. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LalatenduMohanty, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
5 participants
They went into candidate without architecture qualifiers in 0157b7b (#229) with an explicit decision to go multi-arch in db17a23. But for some reason had arch guards when they went into fast with cb27d43 (#162) and 9d10713 (#178) and stable with 74b433b (#163) f652963 (#179).