WIP: NO-JIRA: Internalize registry/client that is removed in distribution/v3#2070
WIP: NO-JIRA: Internalize registry/client that is removed in distribution/v3#2070ardaguclu wants to merge 2 commits intoopenshift:masterfrom
Conversation
|
@ardaguclu: This pull request explicitly references no jira issue. 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 openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ardaguclu The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
@ardaguclu: 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-sigs/prow repository. I understand the commands that are listed here. |
|
These PRs are an experimentation how to upgrade distribution/v3 to newer version. I'm closing them for now. |
|
@ardaguclu: 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-sigs/prow repository. |
This is for testing. First commit comes from #2068 but second commit tries to internalize registry/client (not from the latest version of distribution/distribution/v3, directly from vendored version).
This won't enable the upgrade of distribution/v3 to v3.0.0. Because v3.0.0 contains many other breaking changes. But internalizing registryclient will pave the way for other changes.