Maintenance only status

[Meijuh]

The README indicates this project is in maintenance only, but it is not clear what this means exactly. Currently, Spring framework's 7 resilience features are quite limited. It provides no policy composition, stateful retries or circuit breaking. Hence, the suggestion to migrate might not be feasible for everybody.
W.r.t. stateful retry, the migration guide mentions classes that do not exist in this repo, nor in the Spring Framework repo, what is going here?
Will this Spring Retry project be compatible with Spring Framework 7, and Spring Boot 4? If no, is there any public documentation (e.g., ADLs) with argumentation on this decision, suggested migration strategies and future plans for Spring Resilience? Is there an official channel where the community discusses the new Spring 7 Resilience features?

Not sure if this is the right place to ask; but what would be a valid practical case to limit concurrency at compile time, referring to @ConcurrencyLimit? Is a runtime circuit breaker not a better alternative to reduce concurrency?

[artembilan]

The Spring Retry is still compatible with Spring Framework 7.x generation.
However you would need to manage that dependency yourself.
Please, consult with this blog post about Spring Framework Resilience features: https://spring.io/blog/2025/09/09/core-spring-resilience-features.

The stateful retry and circuit breaker (and rate limiter) could be used from Spring Integration as you have pointed in your post in regards to its migration guide: https://docs.spring.io/spring-integration/reference/handler-advice/classes.html

The https://github.com/spring-projects/spring-framework/issues is now a proper place to raise concerns and share ideas.