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

Remove code deprecated in 2.2 #22034

Closed
scottfrederick opened this issue Jun 19, 2020 · 5 comments
Closed

Remove code deprecated in 2.2 #22034

scottfrederick opened this issue Jun 19, 2020 · 5 comments
Assignees
Labels
type: task A general task
Milestone

Comments

@scottfrederick
Copy link
Contributor

Most code marked as deprecated since 2.2 was removed in 2.3, before we decided that it would be better to leave deprecated APIs in place for two minor releases before deleting. Following this direction, code marked as deprecated since 2.2 should be removed in 2.4.

See issues #19597 and #19860, as well as commits de1a26c and afb6788.

@scottfrederick scottfrederick added this to the 2.4.x milestone Jun 19, 2020
@scottfrederick scottfrederick added the type: task A general task label Jun 19, 2020
@mpens
Copy link
Contributor

mpens commented Jun 19, 2020

Hi @scottfrederick, just to be sure, do we need to remove all the code marked as deprecated in the version 2.2.x

@spring-projects spring-projects locked and limited conversation to collaborators Jun 20, 2020
@spring-projects spring-projects unlocked this conversation Jun 20, 2020
@philwebb
Copy link
Member

philwebb commented Jun 22, 2020

@mla-mpensdavila The plan is to remove the code deprecated since 2.2 but it's probably best if we handle this one since we need to co-ordinate with the Spring Cloud team.

@mpens
Copy link
Contributor

mpens commented Jun 22, 2020

Hi @philwebb, i would like to help, can you guide me what i need to do? and How can i coordinate this?

@philwebb
Copy link
Member

Thanks for the offer @mla-mpensdavila, but since we need to chat with other Spring teams it's best if we handle this one ourselves.

@mpens
Copy link
Contributor

mpens commented Jun 22, 2020

Thanks for the offer @mla-mpensdavila, but since we need to chat with other Spring teams it's best if we handle this one ourselves.

Great, thanks for the info, I'll looking another task to do..

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: task A general task
Projects
None yet
Development

No branches or pull requests

5 participants