Happy New Year 🎉

Agenda (:00)

• [Brian] WildFly 39 release status

• Scheduled for Thu Jan 15 (next week)

• We have five blockers but they seem to be in hand

• Clustering testsuite hot rod connection failures on SE25

• This is intermittent and seems to be about starting a remote Infinispan, not WF itself, so we can likely reduce it to Critical and defer, if needed

• Clustering topology issue, but we have a workaround if need be

• Undertow release -- WIP

• WildFly Galleon Plugins release -- will happen once WildFly Core is released

• JBoss Metadata release -- WIP; discussion here

• Nightly CI results are acceptable, except perhaps the Clustering hot rod issue mentioned above

• TCK results look good.

• [Brian] Move WildFly Core to direct deploy to Maven Central?

• Note: we can likely defer this discussion or drop it as the JBoss Nexus issues we had in Dec seem to be better now

• With WF 39 Beta we learned that there is a basic element of "staging" when deploying directly. You upload content and then release it. It's not a "staging repo" that maven consumers can access to test your release, but it does allow basic sanity checking and avoiding half-way releases.

• A basic issue with deploying directly is getting needed perms; we have established mechanisms for controlling perms via JBoss Nexus.

• [Brian] I did some initial work on setting things up for a separate wildfly-ee-10 FP

• WIP is at https://github.com/bstansberry/wildfly/tree/legacy-fp

• Will need a WildFly feature issue and proposal

• basically creates a new FP structure + ee-build / ee-dist, does some initial TS setup stuff

• TODO

• user boms

• full build + dist (i.e. wildfly-ee-10 + wildfly)

• complete TS integration

• Doc/downloads (using a different archive to stay on Jakarta EE 10)

• Uses "ee-10" as a segment of the artifactId of the user-relevant artifacts (e.g. the FP itself, the channel, user boms etc). This will need to change over time, e.g. if we do an EE 11 one once standard WildFly moves to EE 12.

• Other "internal" artifacts use "legacy-ee" so they will not need to change.

• Status of Java 25 support for WildFly

• WildFly Component SE 25 Support

• FYI about interesting discussions

• Hibernate ORM 6.6 update to allow bytecode enhancement with SE 25

• Link to a zulip, wildfly-dev, google group etc discussion

End of meeting (:33)