Skip to content
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

Tracking issue for dropping code deprecated in v1.3 release #7713

Closed
8 tasks done
ykakarap opened this issue Dec 8, 2022 · 24 comments
Closed
8 tasks done

Tracking issue for dropping code deprecated in v1.3 release #7713

ykakarap opened this issue Dec 8, 2022 · 24 comments
Assignees
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@ykakarap
Copy link
Contributor

ykakarap commented Dec 8, 2022

The following parts of the code base were deprecated in the previous release (v1.3). This is a tracking issue for all the work that needs to be done to drop all the deprecated work:

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Dec 8, 2022
@oscr
Copy link
Contributor

oscr commented Dec 12, 2022

@ykakarap I suggest making each item it's own ticket and using this ticket as an overview. Then each ticket can be discussed and assigned separately, to avoid having multiple people working on the same task. I also suggest each item should include updating the docs :)

@ykakarap
Copy link
Contributor Author

@ykakarap I suggest making each item it's own ticket and using this ticket as an overview.

That is the intention 🙂. I will leave it to whoever picks up an item to create a PR and if they want an issue to go with it.

I also suggest each item should include updating the docs :)

+1

@ykakarap
Copy link
Contributor Author

/help

@k8s-ci-robot
Copy link
Contributor

@ykakarap:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

/help

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.

@k8s-ci-robot k8s-ci-robot added the help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. label Dec 12, 2022
@fabriziopandini
Copy link
Member

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Dec 14, 2022
@chiukapoor
Copy link
Contributor

Hello Team, I will work on the task to Drop clusterctl restore command

@oscr
Copy link
Contributor

oscr commented Dec 16, 2022

@chiukapoor Great to hear! I suspect you should be able to look at #7752 for inspiration. Note the apidiff test will fail for your pr and this is expected.

@chiukapoor
Copy link
Contributor

Sure @oscr, will refer to #7752 :)

/assign

@sbueringer
Copy link
Member

sbueringer commented Jan 2, 2023

@ykakarap Just a note. For some of the sub-tasks we have to update .golangci.yaml. Can you please add that to the respective sub-tasks? (e.g.

cluster-api/.golangci.yml

Lines 222 to 225 in de575ca

# Specific exclude rules for deprecated fields that are still part of the codebase. These should be removed as the referenced deprecated item is removed from the project.
- linters:
- staticcheck
text: "SA1019: (bootstrapv1.ClusterStatus|clusterv1.ClusterTopologyManagedFieldsAnnotation|scope.Config.Spec.UseExperimentalRetryJoin|DockerMachine.Spec.Bootstrapped|machineStatus.Bootstrapped) is deprecated"
)

@knabben
Copy link
Member

knabben commented Jan 3, 2023

hey, I will get these subtasks, PRs follows -

@knabben
Copy link
Member

knabben commented Jan 4, 2023

/reopen

@k8s-ci-robot
Copy link
Contributor

@knabben: Reopened this issue.

In response to this:

/reopen

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.

@k8s-ci-robot k8s-ci-robot reopened this Jan 4, 2023
@sbueringer
Copy link
Member

sbueringer commented Jan 5, 2023

Quick update: after recent PRs that now only leaves the removal of clusterctl restore

@ykakarap
Copy link
Contributor Author

ykakarap commented Jan 6, 2023

Looks like @chiukapoor Is already assigned to that item. Once that is done I will close this issue.

@hackeramitkumar
Copy link
Member

@chiukapoor are you working on 'clusterctl restore' task?? If not then I can take it.

@chiukapoor
Copy link
Contributor

Hey @hackeramitkumar, I have started the work will push changes in couple of days.

@hackeramitkumar
Copy link
Member

@chiukapoor , thank you

Hey @hackeramitkumar, I have started the work will push changes in couple of days.

@hackeramitkumar
Copy link
Member

@chiukapoor are you still working on cluster restore task? Actually we have to done it before the next patch release.

@sbueringer
Copy link
Member

sbueringer commented Jan 18, 2023

@chiukapoor are you still working on cluster restore task? Actually we have to done it before the next patch release.

We don't have to do it before the next patch release as the change will be done on main and the next release "from main" will be the first v1.4 beta.

@ykakarap
Copy link
Contributor Author

Echoing what @sbueringer said, this does not block the next v1.3 and v1.2 patch releases.

It would just be nice to get done to close the deprecation work on main. 🙂

@sbueringer
Copy link
Member

sbueringer commented Jan 19, 2023

Thx @hackeramitkumar for taking over the last part.

Thx everyone!

/close

@k8s-ci-robot
Copy link
Contributor

@sbueringer: Closing this issue.

In response to this:

Thx @hackeramitkumar for taking this over.

Thx everyone!

/close

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.

@ykakarap
Copy link
Contributor Author

Thank you everyone who worked on this issue! 🙏🏼

@fabriziopandini
Copy link
Member

dream team!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

8 participants