End of Community Support for 2.0.x & 3.0.x

[sbordet]

The Jetty Reactive HttpClient project announces the End of Community Support for versions 2.0.x and 3.0.x, following Jetty's announcement of End of Community Support for Jetty 10.0.x and 11.0.x.

September 1st, 2024 marks the official End of Community Support for Jetty Reactive HttpClient 2.0.x & 3.0.x.

While users of Jetty Reactive HttpClient 2.0.x & 3.0.x will continue to see releases for security and critical issues until Jetty Reactive HttpClient 2.0.x & 3.0.x go End of Life, the only on-demand support provided will be for Webtide customers.

As for the official End of Life of Jetty Reactive HttpClient 2.0.x & 3.0.x, we will give at least 6 months notice after the last Webtide customer has transitioned off of using Jetty 10.0.x & 11.0.x. We can’t provide a firm date, but it is unlikely to happen before 2025.

Thank you for your continued usage and support of Jetty Reactive HttpClient.
Please take a moment to look at the newer Jetty Reactive HttpClient release 4.0.x.

Action	Before September 1st, 2024	End of Community Support (September 1st, 2024)	End of Life (Date TBD)
Community PRs reviewed and integrated	✔️	❌	❌
Webtide Customer PRs reviewed and integrated	✔️	✔️	❌
Community triggered releases	✔️	❌	❌
Webtide Customer triggered releases	✔️	✔️	❌
Security / Vulnerability triggered releases	✔️	✔️	❌