On May 20, 2016, at 5:05 PM, arjan tijms <arjan.tijms(a)gmail.com> wrote:
Just wondering, but will WildFly 10.1 be the basis for a future EAP 8, or for a future
How are the WildFly and EAP branches related to each other now that EAP 7 final has been
A number of the features developed in WildFly 11 will be backported into the EAP 7.1
branch. Some of them might carry over into a 7.2 release. EAP8 is pretty far out, so there
will be a number of community releases in between.
> On Fri, May 20, 2016 at 11:45 PM, Jason Greene <jason.greene(a)redhat.com>
> Hello Everyone,
> I’d like to cut a 10.1 fairly soon, preferably in the next 2-3 weeks. My thinking is
to take everything that is not explicitly tagged as 11.x and merge it ASAP. Really this
should just be anything that doesn’t add instability, or introduces a half-finished API
that we then have to support (the obvious exception is experimental capabilities that we
denote as such). This is a bit of a departure from what I was suggesting earlier, where we
we would cherry-pick major items into a separate branch, so if you have any concerns now
is the time to raise them.
> This release would be a good opportunity to include features that are ready to go
(suitable for a final release in 2-3 weeks) but didn’t make 10.0 (I have a feeling Sanne
has been itching for some updates to search!). If you have something then send a PR
(noting that you want it in 10.1) or raise your figurative hand :)..
> Jason T. Greene
> WildFly Lead / JBoss EAP Platform Architect
> JBoss, a division of Red Hat
> wildfly-dev mailing list