@Julian Ladisch: @Taras Spashchenko said not much work to bump to 21. @Ingolf Kuss agrees.
@Julian Ladisch Will also need 21 for Keycloak for Eureka.
@Craig McNally We're on Keycloak 25. Was unaware that Keycloak had deprecated JDK 17 support.
@Jenn Colt will leave this question open.
@Marc Johnson The work for JDK 21 is not development work; it's tooling. We don't know if there is community capacity for that work. And don't know if the devops contract with Index Data includes that work; if not, would have to find folks who will. Also not sure why we're talking about Eureka in this context, since it's not adopted by the community yet on any timeline.
@Jenn Colt Is talking to Index Data then a missing step in the OSTs?
@Marc Johnson Depends on what change we are making. If one of these decisions, i.e. Java or yarn-to-npm, has a burden on how we build the system, then have to include those stakeholders. Similarly if it had a developer impact, should talk to the developers. There should be a step between "this would be a good idea for this release" to "can we actually achieve it".
@Craig McNally Keycloak 25 supports but deprecates JDK 17. Once Keycloak 26 comes out, JDK 17 support is removed in favor of JDK 21. Keycloak only supports the current version, so would need to upgrade to Keycloak 26 and JDK 21 at least for Keycloak. If running FOLIO in Docker containers there is not much tooling, just use a different base image. No code to be compiled.
@Marc Johnson Agree with Craig. Building from source would be different. But Keycloak is not currently in the scope of OST. If we want Eureka supported, then Keycloak and other tools need to be in the OST. At that point it's worth talking about Java version conflicts. Talking several steps ahead.
@Julian Ladisch By keeping 17, we indirectly make a decision to not allow Keycloak / Eureka on Sunflower. There is a group of German sysops who want to do a test installation of Eureka. But that's not the main point. Developers wanted to move to JDK 21. Should have a good argument on why not to switch to 21. Jenkins support should be possible. Docker container completed yesterday for JDK 21. No reason to reject 21 for Sunflower.
@Marc Johnson If folks in the community are willing to commit to those build infrastructure changes on the schedule for Sunflower, then nothing stops 21. That's the constraint.
@Jenn Colt Community hasn't decided on Eureka, but to support experimentation with it is a positive.
@Jenn Colt and @Craig McNally will follow up with Index Data.
@Marc Johnson Given the confusion happening here, we need something that guides folks making changes, when and how to talk to the TC about it.
@Tod Olson The time to raise this is "as early as possible". Pushing OST earlier as we did is good. Gap may be not reaching out to the stakeholders. Someone should not have to bring an upgrade issue to us, for us to reach out. More meeting in the middle.
@Marc Johnson We talked today about putting notifications out at various points in the process. Messaging needs to be different at different stages. Put out a draft for a release, announce it, invite contact to TC within X period of time (6w-2m?) if you are interested in discussion. Gives them enough time to think, gives us enough time to get process done by when we need. I.e. talking about X decision on a particular date. If they don't turn up, they don't. At later point, we announce it – barring 1st party library changes, this is the tech choices for this release.