I am +1 on 6.0 as well. The other topics brought up on this thread are important, and we should address them, but I think we can move forward with the version decision in parallel.
Jordan On Thu, Apr 10, 2025 at 11:50 AM Brad <bscho...@gmail.com> wrote: > > . I assume JDK 21 may lead to removal of JDK 11 which is breaking change > > If we name it 6.0, I would hope we bump both Java and Python supported > versions to align with their EOL status. > > - Java 11 with OpenJDK EOL was October 2024 > - Python 3.8 EOL was October 7, 2024 > > > On Thu, Apr 10, 2025 at 2:44 PM Ekaterina Dimitrova <e.dimitr...@gmail.com> > wrote: > >> +1 on calling it 6.0. I assume JDK 21 may lead to removal of JDK 11 which >> is breaking change (people need to upgrade to the common JDK version - 17 >> before upgrading to the next release) >> >> On Thu, 10 Apr 2025 at 14:40, Štefan Miklošovič <smikloso...@apache.org> >> wrote: >> >>> +1, I am also getting questions about the versioning recently and people >>> themselves do not know what to call the next version like. >>> >>> On Thu, Apr 10, 2025 at 8:28 PM Jon Haddad <j...@rustyrazorblade.com> >>> wrote: >>> >>>> Bringing this back up. >>>> >>>> I don't think we have any reason to hold up renaming the version. We >>>> can have a separate discussion about what upgrade paths are supported, but >>>> let's at least address this one issue of version number so we can have >>>> consistent messaging. When i talk to people about the next release, I'd >>>> like to be consistent with what I call it, and have a unified voice as a >>>> project. >>>> >>>> Jon >>>> >>>> On Thu, Jan 30, 2025 at 1:41 AM Mick Semb Wever <m...@apache.org> wrote: >>>> >>>>> . >>>>> >>>>> >>>>>> If you mean only 4.1 and 5.0 would be online upgrade targets, I would >>>>>> suggest we change that to T-3 so you encompass all “currently supported” >>>>>> releases at the time the new branch is GAed. >>>>>> >>>>>> I think that's better actually, yeah. I was originally thinking T-2 >>>>>> from the "what calendar time frame is reasonable" perspective, but saying >>>>>> "if you're on a currently supported branch you can upgrade to a release >>>>>> that comes out" makes clean intuitive sense. That'd mean: >>>>>> >>>>>> 6.0: 5.0, 4.1, 4.0 online upgrades supported. Drop support for 4.0. >>>>>> API compatible guaranteed w/5.0. >>>>>> 7.0: 6.0, 5.0, 4.1 online upgrades supported. Drop support for 4.1. >>>>>> API compatible guaranteed w/6.0. >>>>>> 8.0: 7.0, 6.0, 5.0 online upgrades supported. Drop support for 5.0. >>>>>> API compatible guaranteed w/7.0. >>>>>> >>>>> >>>>> >>>>> >>>>> I like this. >>>>> >>>>>
