[wildfly-dev] WildFly Core component upgrade coordination

jose.e.chavez at gmail.com jose.e.chavez at gmail.com
Mon Oct 13 08:49:59 EDT 2014


<div name="BB10" id="BB10_response_div" dir="auto" contenteditable="true"                                                                                             style="width:100%;background:&quot;#ffffff&quot;; font-size: initial;font-family:&quot;Calibri&quot;,&quot;Slate Pro&quot;,&quot;sans-serif&quot;;color:#1f497d;"><br style="display:initial"></div>                                                                                                                                     <div name="BB10" id="response_div_spacer" dir="auto" contenteditable="true"                                                                                           style="width:100%;background:&quot;#ffffff&quot;; font-size: initial;font-family:&quot;Calibri&quot;,&quot;Slate Pro&quot;,&quot;sans-serif&quot;;color:#1f497d;"><br style="display:initial"></div>                                                                                                                                     <div id="_signaturePlaceholder" name="BB10" dir="auto"  contenteditable="true"                                                                                      style="font-size: initial;font-family:&quot;Calibri&quot;,&quot;Slate Pro&quot;,&quot;sans-serif&quot;;color:#1f497d;"></div>                                       <table id="_bb10TempSeparator" width="100%" style="background-color:white; border-spacing:0px;" contenteditable="false">                                               <tr><td></td><td id="_separatorInternal" rowspan=2 style="text-align:center">                                                                                            <span id="_bb10TempSeparatorText" style="background-color:white; color:#0073BC;font-size:smaller;font-family:&quot;Slate Pro&quot;">&nbsp; Original Message &nbsp;</span>      </td></tr>                                                                                                                                                               <tr> <td colspan=2><div style="border:none;border-top:solid #0073BC 1.0pt;">                                                                                           </td></tr></table>                                                                                                                                                 <table width="100%" style="background-color:white;border-spacing:0px;"> <tr><td id="_persistentHeaderContainer" colspan=2>                                              <div id="_persistentHeader" style="font-size: smaller;font-family:&quot;Tahoma&quot;,&quot;BB Alpha Sans&quot;,&quot;Slate Pro&quot;,&quot;sans-serif&quot;;">  <div id=From ><b>From: </b>Darran Lofthouse</div><div id=Sent ><b>Sent: </b>Monday, October 13, 2014 5:33 AM</div><div id=To ><b>To: </b>Stuart Douglas; David M. Lloyd</div><div id=Cc ><b>Cc: </b>wildfly-dev at lists.jboss.org</div><div id=Subject ><b>Subject: </b>Re: [wildfly-dev] WildFly Core component upgrade coordination</div></div></td></tr></table><div id="_persistentHeaderEnd" style="border:none;border-top:solid #babcd1 1pt;"></div><br><div name="BB10" dir="auto" id="_originalContent">On 10/10/14 23:37, Stuart Douglas wrote:<br/>&gt; I meant in the general case, not this week in particular :-)<br/><br/>+1 I think from a predictability perspective for the majority of <br/>engineers this means that it is the start of the week that they see <br/>Wildfly with an updated core which overall is what we are trying to meet.<br/><br/>&gt; Stuart<br/>&gt;<br/>&gt; David M. Lloyd wrote:<br/>&gt;&gt; We just did a release Tuesday, so why don&apos;t we start next week instead?<br/>&gt;&gt;<br/>&gt;&gt; On 10/10/2014 04:28 PM, Stuart Douglas wrote:<br/>&gt;&gt;&gt; If no one else gets to I can do it first thing Monday (Sunday for<br/>&gt;&gt;&gt; everyone else).<br/>&gt;&gt;&gt;<br/>&gt;&gt;&gt; Stuart<br/>&gt;&gt;&gt;<br/>&gt;&gt;&gt; Jason Greene wrote:<br/>&gt;&gt;&gt;&gt; I don’t think Stuart officially volunteered? Don’t forget that our<br/>&gt;&gt;&gt;&gt; Friday is his Saturday, and his Friday is our Thursday.<br/>&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt; Brain volunteered though. I was planning on doing it, but if he (or<br/>&gt;&gt;&gt;&gt; anyone else is up for thats great), he (or anyone else) can continue<br/>&gt;&gt;&gt;&gt; to charge me beer debt :)<br/>&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt; On Oct 10, 2014, at 8:38 AM, David M. Lloyd&lt;david.lloyd at redhat.com&gt;<br/>&gt;&gt;&gt;&gt; wrote:<br/>&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt;&gt; OK so it seems like we have a sort of consensus here. To summarize:<br/>&gt;&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt;&gt; • WildFly Core releases will happen at some nonspecific time on each<br/>&gt;&gt;&gt;&gt;&gt; Friday (but only if there have actually been changes that warrant a<br/>&gt;&gt;&gt;&gt;&gt; release, of course, i.e. there&apos;s something that would block somebody&apos;s<br/>&gt;&gt;&gt;&gt;&gt; progress in some area)<br/>&gt;&gt;&gt;&gt;&gt; • Release will be done by Stuart or another core team member as<br/>&gt;&gt;&gt;&gt;&gt; appropriate/needed<br/>&gt;&gt;&gt;&gt;&gt; • Merge team will make a best effort to merge everything that is marked<br/>&gt;&gt;&gt;&gt;&gt; ready-for-merge by Thursday end-of-day<br/>&gt;&gt;&gt;&gt;&gt; • People submitting changes should have no reasonable expectation that<br/>&gt;&gt;&gt;&gt;&gt; last minute changes will be merged unless they are trivial<br/>&gt;&gt;&gt;&gt;&gt; • All WildFly Core update JIRAs will be parented to this JIRA:<br/>&gt;&gt;&gt;&gt;&gt; https://issues.jboss.org/browse/WFLY-3956<br/>&gt;&gt;&gt;&gt;&gt; • Since the last release was this past Tuesday, we&apos;ll start this no<br/>&gt;&gt;&gt;&gt;&gt; sooner than next week<br/>&gt;&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt;&gt; I think that&apos;s about it. I&apos;m sure you all will correct me if I missed<br/>&gt;&gt;&gt;&gt;&gt; something. :)<br/>&gt;&gt;&gt;&gt;&gt; --<br/>&gt;&gt;&gt;&gt;&gt; - DML<br/>&gt;&gt;&gt;&gt;&gt; _______________________________________________<br/>&gt;&gt;&gt;&gt;&gt; wildfly-dev mailing list<br/>&gt;&gt;&gt;&gt;&gt; wildfly-dev at lists.jboss.org<br/>&gt;&gt;&gt;&gt;&gt; https://lists.jboss.org/mailman/listinfo/wildfly-dev<br/>&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt; --<br/>&gt;&gt;&gt;&gt; Jason T. Greene<br/>&gt;&gt;&gt;&gt; WildFly Lead / JBoss EAP Platform Architect<br/>&gt;&gt;&gt;&gt; JBoss, a division of Red Hat<br/>&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt;<br/>&gt;&gt;&gt;&gt; _______________________________________________<br/>&gt;&gt;&gt;&gt; wildfly-dev mailing list<br/>&gt;&gt;&gt;&gt; wildfly-dev at lists.jboss.org<br/>&gt;&gt;&gt;&gt; https://lists.jboss.org/mailman/listinfo/wildfly-dev<br/>&gt;&gt;<br/>&gt; _______________________________________________<br/>&gt; wildfly-dev mailing list<br/>&gt; wildfly-dev at lists.jboss.org<br/>&gt; https://lists.jboss.org/mailman/listinfo/wildfly-dev<br/>&gt;<br/>_______________________________________________<br/>wildfly-dev mailing list<br/>wildfly-dev at lists.jboss.org<br/>https://lists.jboss.org/mailman/listinfo/wildfly-dev



More information about the wildfly-dev mailing list