WildFly 40 Schedule Update
by Brian Stansberry
We've decided to push out the WildFly 40 schedule by 1 week. The PR
deadline for 40 Beta *was* next Wednesday, but we've moved all the
dates out by a week.
The key dates are:
WildFly 40 Beta:
PRs due: Wed, April 1 (no fooling)
Tag and deploy: Wed, April 8
Finish and announce release: Thu, April 9
WildFly 40 Final:
PRs due: Wed, April 15
Tag and deploy: Wed, April 22
Finish and announce release: Wed, April 23
I've updated https://www.wildfly.org/events/#calendar with the new dates.
Best regards,
Brian
1 month, 1 week
PR testing with SE 25
by Brian Stansberry
We're continuing to progress with qualifying SE 25 as our recommended
SE version for WildFly. That's getting close enough that we should
look at what we're doing for PR testing. Currently full WF and WF Core
are not testing PRs on SE 25. We're relying on nightly jobs to detect
problems.
A difficulty is CI is a limited resource and we also want to limit our
carbon impact, so just adding more jobs for each PR doesn't seem good.
Perhaps....
On full WF...
Replace the "Linux MicroProfile - JDK 17" job with a 'Linux - JDK 25".
The "Linux MicroProfile" job runs a subset of tests but with server
installation the run the standalone-microprofile.xml config instead of
standalone.xml. It basically validates that the presence of the MP
stuff in the config doesn't break things. I can't remember the last
time that test detected a problem. Probably not the decade. It brings
little value.
Replacing it with a full -DallTests job will mean more resource
consumed per PR though.
On Core....
Reconfigure "WildFly Core -> Preview Integration Linux- JDK 21" to use
SE 25 instead.
That leaves nothing running the core TS on 25 though. Perhaps we could
remove the -DskipTests setting in the step in "WildFly Core -> Preview
Integration Linux- JDK 21" that builds core.
WDYT?
- Brian
1 month, 2 weeks
