<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>On May 20, 2016, at 5:05 PM, arjan tijms <<a href="mailto:arjan.tijms@gmail.com">arjan.tijms@gmail.com</a>> wrote:</div><div><br></div><blockquote type="cite"><div><div dir="ltr">Hi Jason,<div><br></div><div>Just wondering, but will WildFly 10.1 be the basis for a future EAP 8, or for a future EAP 7.x?</div><div><br></div><div>How are the WildFly and EAP branches related to each other now that EAP 7 final has been released?</div></div></div></blockquote><div><br></div><div>Hi Arjan,</div><div><br></div><div>Good question.</div><div><br></div><div>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. </div><div><br></div><div>Cheers,</div><div>Jason</div><div><br></div><br><blockquote type="cite"><div><div dir="ltr"><div><br></div><div>Kind regards,</div><div>Arjan Tijms</div><div><br></div><div><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 20, 2016 at 11:45 PM, Jason Greene <span dir="ltr"><<a href="mailto:jason.greene@redhat.com" target="_blank">jason.greene@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello Everyone,<br>
<br>
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.<br>
<br>
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 :)..<br>
<br>
Thoughts?<br>
--<br>
Jason T. Greene<br>
WildFly Lead / JBoss EAP Platform Architect<br>
JBoss, a division of Red Hat<br>
<br>
<br>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org">wildfly-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/wildfly-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/wildfly-dev</a></blockquote></div><br></div>
</div></blockquote></body></html>