Skip to content

Will this merge request about AsyncRequestNotUsableException be added to the milestone of 6.1.x? #33757

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

Closed
hw207165 opened this issue Oct 19, 2024 · 1 comment
Labels
status: invalid An issue that we don't feel is valid

Comments

@hw207165
Copy link

Will this merge request be added to the milestone of 6.1.x?

dbc6928#diff-2561f5cef97c1c92815616fd4e3df4f38b8bb92e6e2b0c3c366ebc601b768bd6R51

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged or decided on label Oct 19, 2024
@snicoll
Copy link
Member

snicoll commented Oct 20, 2024

No. We don't do delayed backport so if it's not scheduled when it's closed, it's not meant to be. You can also see a @since on the commit you've shared that confirms it's 6.2 only dbc6928

@snicoll snicoll closed this as not planned Won't fix, can't repro, duplicate, stale Oct 20, 2024
@snicoll snicoll added status: invalid An issue that we don't feel is valid and removed status: waiting-for-triage An issue we've not yet triaged or decided on labels Oct 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: invalid An issue that we don't feel is valid
Projects
None yet
Development

No branches or pull requests

3 participants