-
Notifications
You must be signed in to change notification settings - Fork 65
Enable 4.3.14 in candidate channel(s) #193
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
/lgtm |
|
/lgtm cancel |
a09caf1 to
5ff491a
Compare
LalatenduMohanty
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: LalatenduMohanty, openshift-bot 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 |
| @@ -1,5 +1,6 @@ | |||
| name: candidate-4.4 | |||
| versions: | |||
| - 4.3.14+amd64 | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
oops ,not sorted
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had assumed this was a requirement of our new robot masters.
Generated with: $ hack/backfill.py $ git checkout HEAD -- channels/candidate-4.3.yaml $ emacs channels/candidate-4.4.yaml With the candidate-4.3 and 4.4 massaging so we don't get: - 4.3.14 +- 4.3.14+amd64 and similar, where all arches went into candidate-4.3, but only amd64 went into the candidate-4.4, 5ff491a (Enable 4.3.14 in candidate channel(s), 2020-04-22, openshift#193).
Generated with: $ hack/backfill.py $ git checkout HEAD -- channels/candidate-4.3.yaml $ emacs channels/candidate-4.4.yaml $ git checkout HEAD -- channels/stable-4.6.yaml With the candidate-4.3 and 4.4 massaging so we don't get: - 4.3.14 +- 4.3.14+amd64 and similar, where all arches went into candidate-4.3, but only amd64 went into the candidate-4.4, 5ff491a (Enable 4.3.14 in candidate channel(s), 2020-04-22, openshift#193). The stable-4.6 massaging is because we are delaying the 4.5->4.6 stable updates while we convince ourselves that fast traffic is sufficiently reliable.
Generated with: $ hack/backfill.py $ git checkout HEAD -- channels/candidate-4.3.yaml $ emacs channels/candidate-4.4.yaml $ git checkout HEAD -- channels/stable-4.6.yaml With the candidate-4.3 and 4.4 massaging so we don't get: - 4.3.14 +- 4.3.14+amd64 and similar, where all arches went into candidate-4.3, but only amd64 went into the candidate-4.4, 5ff491a (Enable 4.3.14 in candidate channel(s), 2020-04-22, openshift#193). The stable-4.6 massaging is because we are delaying the 4.5->4.6 stable updates while we convince ourselves that fast traffic is sufficiently reliable.
Please merge immediately. This PR does not need to wait for an advisory to ship, but the associated advisory is https://errata.devel.redhat.com/advisory/53642 .
This PR will also enable upgrades from 4.3.14 to releases in candidate-4.4