Have it for *at least* 1 MAJOR in deprecated status (deprecate-then-remove)
This reads to me that Java 17 would need to be deprecated now, continue to be deprecated in 6.0 (at least one major in deprecated), then removed in 7.0. On Wed, Apr 23, 2025 at 10:54 AM Ekaterina Dimitrova <e.dimitr...@gmail.com> wrote: > I think there is no reason to deprecate 17 in 5.0? > > I’d think we would deprecate at some point 11 in 5.0, (once the community > is confident in 17 being prod ready.) We commit 21 in 6.0 with the plan to > remove 11 and switch to 17 builds in 6.0. Any other thoughts? Points of > view? > > On Wed, 23 Apr 2025 at 13:42, Jon Haddad <j...@rustyrazorblade.com> wrote: > >> So to be clear - are we simultaneously calling Java 17 in 5.0 deprecated >> AND experimental? >> >> >> >> On Wed, Apr 23, 2025 at 10:23 AM Joseph Lynch <joe.e.ly...@gmail.com> >> wrote: >> >>> +1 given "Have it for *at least* 1 MAJOR in deprecated status >>> (deprecate-then-remove)" >>> >>> How does that sit with you Joey? >>>> >>> Great! Really appreciate the clarification! >>> >>> -Joey >>> >>
