On Thu, Nov 4, 2021 at 10:42 AM Dawid Weiss <dawid.we...@gmail.com> wrote: > > > we don't have to "support" users on our main trunk branch. That's why > > we make releases. > > Nah. I don't agree with this one - you have to be aware about who is > using your project (especially a library) and in what context. Maybe > we differ in our opinion here. Your previous argument is much more > convincing (thank you for laying it out so clearly). >
Let's try again. First of all, I feel Uwe's reply says it perfectly, so it is difficult to elaborate more. But there should be a place to add "latest-and-greatest" changes, that take advantage of whatever new slim pickings java will give us. This allows the project to move forward: both in terms of new opportunities, but also basic janitorial work: so you don't have a ton of slow suboptimal code that doesn't "keep with the times". This is what a 'main' branch is all about: it is the latest and greatest. We have stable branches such as 'branch_9x' which stay stable on their old java 11, and maybe we spin 10 releases for them for 2.5 years just like we did for 8.x Plenty of bugfixes/improvements can be backported to 'branch_9x', maybe they require some small modifications because 'branch_9x' is on java 11. When this gets to be painful it is a sign that lucene 10 is overdue, and we branch again :) So it really shouldn't be controversial for the main branch to have the latest dependencies and so on. But yet we suffer through this battle *EVERY SINGLE MAJOR LUCENE RELEASE*. Like pulling teeth to bump the jdk version so that we can improve its features. Doesn't make any sense as the change won't have user impact for 2.5 years. In this case, in 2.5 years (2023), JDK11 will actually be EOL already. No sense in holding back 10.x like that. --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
