<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:trebuchet ms,sans-serif"><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 29, 2020 at 7:19 PM James Perkins <<a href="mailto:jperkins@redhat.com">jperkins@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div dir="ltr">Hi Brian,<br></div><div dir="ltr"><br></div><div>+1 from me with the question below on point 2.<br></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 29, 2020 at 9:42 AM Brian Stansberry <<a href="mailto:brian.stansberry@redhat.com" target="_blank">brian.stansberry@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div style="font-family:"trebuchet ms",sans-serif">In my announcement of the WildFly 19 Beta1 release I said that we'd likely delay the Final release a bit to evaluate the possibility of supporting MicroProfile 3.3, which is due out in February. Our investigations of that are looking favorable, so I'd like to propose the following:</div><div><br></div><div><div style="font-family:"trebuchet ms",sans-serif">1) Delay the WildFly 19 Final release until shortly after the approximately Feb 18 MicroProfile 3.3 release in order to bring it in.</div><div style="font-family:"trebuchet ms",sans-serif"><br></div><div><font face="trebuchet ms, sans-serif">2) We m</font>ake next Fri Feb 7 the cutoff for having other changes for 19 merged into master. For changes going into WildFly Core the cutoff would be next Tue Feb 4.</div></div></div></blockquote><div><br></div><div>Does this mean features or just bug fixes?</div></div></div></blockquote><div><br></div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif">I'd say just bug fixes, with possible consideration for a feature if there's a very strong case it needs to be in. But in general I think we're done with features other than MP 3.3.</div><div class="gmail_default" style="font-family:"trebuchet ms",sans-serif"></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="gmail_quote"><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><div><br></div><div>3) On Feb 7 create a 19.x branch that we will use for the MicroProfile 3.3 work. WildFly 19 would be released from this branch.</div><div><br></div><div>4) This means from that point the master branch would be open for work on WildFly 20.</div><div><br></div><div>5) Any very high priority bug fixes we identify before 19 Final we would also port to 19.x. But the goal should be to have anything we know of now in before we create the branch.</div><div><br></div><div>6) If we hit some issue that makes it look like getting 3.3 in would go past Feb we can reset and release WF 19 with MicroProfile 3.2.</div><br></div><div><div style="font-family:"trebuchet ms",sans-serif">Best regards,</div><div style="font-family:"trebuchet ms",sans-serif">Brian</div><br></div></div>
_______________________________________________<br>
wildfly-dev mailing list<br>
<a href="mailto:wildfly-dev@lists.jboss.org" target="_blank">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 clear="all"><div><br></div>-- <br><div dir="ltr"><div dir="ltr"><div><div dir="ltr"><div>James R. Perkins</div><div>JBoss by Red Hat</div></div></div></div></div></div>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr">Brian Stansberry<div>Manager, Senior Principal Software Engineer</div><div>Red Hat</div></div></div></div>