While chatting with Sebastian …. I think he was talking about something different.
So I was talking about: „Give us 3000€/year and we’ll keep Java 11 on develop“ „give us 1000€/year and we’ll keep Java 17 on develop" I think he meant to go to 21 on develop and maintain a „java 11 compatibility branch“. That’s a huge amount of additional work. Definitely cleaner. However then it would need to be a community effort to maintain them (and not just clicking dependabot emails) Chris Von: Christofer Dutz <[email protected]> Datum: Donnerstag, 14. August 2025 um 09:36 An: [email protected] <[email protected]> Betreff: AW: [DISCUSS] Interesting idea about old-java-version support Well … I’m totally open for suggestions? 3001€ is just as „in between“ as 199€ 😉 Another alternative would be to instantly drop it and point out that people can ask the companies backing PLC4X for Java 11 or even 8 support. I’m fine with either ;-) Just want our approach to be driven by consensus and not what the 3-4 responding want. Chris Von: [email protected] <[email protected]> Datum: Donnerstag, 14. August 2025 um 09:32 An: [email protected] <[email protected]> Betreff: Re: [DISCUSS] Interesting idea about old-java-version support Something in between...as it is definetly more work.. Am 14. August 2025 09:27:41 MESZ schrieb Christofer Dutz <[email protected]>: >Sooooo … I would like to create these open-collective projects. >Which sums should I use? The ones I proposed? Sebastian’s? Or something in >between? > >Chris > > >Von: Cesar Garcia <[email protected]> >Datum: Freitag, 8. August 2025 um 22:46 >An: [email protected] <[email protected]> >Betreff: Re: [DISCUSS] Interesting idea about old-java-version support > >+1 > > >El vie, 8 ago 2025 a las 3:14, Christofer Dutz (<[email protected]>) >escribió: > >> >> Hi all, >> >> Sebasitan had a great idea, which I think initially he meant as a joke, >> but I think the idea is actually really good. >> >> We’re currently struggling a bit that we as maintainers need to stick with >> Java 11 because some users claim to need it. >> >> The thing is, this makes many things a lot harder for us maintainers. As I >> just cut a new release, updating our dependencies before was more >> challenging as for some dependencies I needed to track down the last >> version that supports Java 11. >> >> Also does it prevent us from updating to the latest version. Not all >> projects maintain legacy branches (we don’t either). >> >> So the idea was: >> If this is really so important for some of our users and it’s more work >> for us and potentially harmful for users not stuck at Java 11, how about we >> create an open-collective project. If we get 2k€-3k€/Year, we keep Java 11, >> otherwise we drop it and to to 17 ... or we do multiple campaigns: >> >> * 3k€/year for Java 11 >> * 1k€/year for Java 17 >> Otherwise we go to Java 21? >> And if one version is gone, it’s gonne for good. >> >> We could use the funds to orgaanize community events around PLC4X. >> >> What do you think? >> >> >> Chris >> > > >-- >*CEOS Automatización, C.A.* >*GALPON SERVICIO INDUSTRIALES Y NAVALES FA, C.A.,* >*PISO 1, OFICINA 2, AV. RAUL LEONI, SECTOR GUAMACHITO,* > >*FRENTE A LA ASOCIACION DE GANADEROS,BARCELONA,EDO. ANZOATEGUI* >*Ing. César García* > >*Cel: +58 414-760.98.95* > >*Hotline Técnica SIEMENS: 0800 1005080* > >*Email: [email protected] ><[email protected]>*
