Re: Proposal: EOL for Shiro major versions
Brian Demers <[email protected]> Mon, 8 Jul 2024 13:50:07 -0400
| Newsgroups | gmane.comp.apache.shiro.devel,gmane.comp.jakarta.jmeter.user |
|---|---|
| Message-ID | <CAH9eYVpMJW_mWHP+Jdf9Rs8WUN_zhqGeCsja71yHwTdvafhvBA@mail.gmail.com> |
+0.9 (basically a +1 with a nit) I think we need to get the 3.x out the door before we commit to an official EOL for 2.x, but assuming we get 3.x out in 2024, I think these timelines are reasonable, and +1 specifically for the 1.x EOL end of 2024) One other thing I'd like to see added/fixed on 3.x is the cleanup of our Spring support. https://github.com/apache/shiro/issues/1576 On Tue, Jul 2, 2024 at 12:14 AM <[email protected]> wrote: > Here is my proposal: > > Shiro 1.x EOL at the end of 2024 > Shiro 2.x EOL at the end of 2025 > > Shiro 3.x focus is: > - Jakarta EE (non-shaded) - remove support for Java EE (remove dependency > on javax.* namespace) > - Remove “rawtypes” replace with Generics in the API > - Prune abandoned / deprecated support modules: > - Guice 3? > - Hazelcast / EHcache / etc - replace with JCache > - Quartz > - Anything else? > > Feedback is appreciated!