The primary PR for adding this feature pack is now out of draft state: https://github.com/wildfly/wildfly/pull/19841 Thank you to those who have been looking at it so far. I recognize it's a lot. That branch results in two feature packs providing EE 10. That's because the regular wildfly-ee feature pack is still using EE 10. My next step will be a separate PR based on #19841 that moves standard WildFly to EE 11. On Wed, Apr 1, 2026 at 3:10 PM Brian Stansberry <bstansberry(a)gmail.com&gt; wrote: > > I've talked over the last year or so about providing an EE 10 variant > of standard WildFly once we move standard WildFly on to EE 11. > > That day is approaching rapidly so I need to get moving on this. So: > > Issue: https://github.com/wildfly/wildfly-proposals/issues/818 > > Analysis: https://github.com/wildfly/wildfly-proposals/pull/819 > > I did quite a bit of work on this in January and am taking it back up. > > We're closing in rapidly on WildFly Preview being EE 11 compatible and > it seems highly likely that can be achieved by the planned April 23 WF > 40 release. > > Once WFP is compatible it's a matter of maybe a day's work to shift > standard WildFly to providing EE 11 instead of EE 10. So that could be > done for WF 40 as well. But, unlike WFP, standard WF hasn't been > providing EE 11 APIs for a number of releases, so if we shift std WF > to EE 11 APIs we'd want to do that for 40 Beta, which is scheduled for > release next week. > > When we move std WF to EE 11, we also want to provide this EE 10 > feature pack, and continue to provide it for a couple quarters, to > give our users a chance to adapt to EE 11 while still getting bug > fixes and other new features. It would be good to provide this with 40 > Beta as well. > > So, there's a lot going on. > > On tomorrow's WildFly Community Call (9 AM EDT at > https://meet.google.com/gwx-xggw-taj) we'll be talking about all this. > Please join us! > > Best regards, > > Brian Stansberry > WildFly project lead