<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Thanks, Denis !!!<div><br></div><div>Best regards,<br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">/Xavier<br><br><br></span>
</div>
<br><div><div>On Jun 17, 2013, at 9:40 PM, Brian Fitzpatrick wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Thanks to some help from Denis, WS tests are now blue! <br><br>Thanks Denis!<br><br>Still hoping for some help from Rob Stryker on the ESB test failures.<br><br>_______________________________<br>Brian Fitzpatrick (aka "Fitz")<br>Senior Software Engineer, SOA-P<br>JBoss by Red Hat<br><br>----- Original Message -----<br>From: "Brian Fitzpatrick" <<a href="mailto:bfitzpat@redhat.com">bfitzpat@redhat.com</a>><br>To: "Max Rydahl Andersen" <<a href="mailto:manderse@redhat.com">manderse@redhat.com</a>><br>Cc: "jbosstools-dev jbosstools-dev" <<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>><br>Sent: Thursday, June 13, 2013 2:32:21 PM<br>Subject: Re: [jbosstools-dev] ACTION REQUIRED: core Beta2<span class="Apple-tab-span" style="white-space:pre"> </span>branch/codefreeze<span class="Apple-tab-span" style="white-space:pre"> </span>Thursday - steps inside<br><br>ESB and Web Services both are running with yellow builds (not green) right now. Have branched and cleaned up JIRAs for 4.1.0.Beta2.<br><br>The issues remaining are: JBIDE-14866 (ESB, asking Rob Stryker for help - builds and tests fine locally, but not on Jenkins) and JBIDE-14867 (WS, looking into now)<br><br>So unfortunately ESB & WS are not going to be ready for code freeze because of these two test issues.<br><br>_______________________________<br>Brian Fitzpatrick (aka "Fitz")<br>Senior Software Engineer, SOA-P<br>JBoss by Red Hat<br><br>----- Original Message -----<br>From: "Max Rydahl Andersen" <<a href="mailto:manderse@redhat.com">manderse@redhat.com</a>><br>To: "jbosstools-dev jbosstools-dev" <<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a>><br>Sent: Tuesday, June 11, 2013 8:12:35 AM<br>Subject: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze<span class="Apple-tab-span" style="white-space:pre"> </span>Thursday - steps inside<br><br>Hi core-compnent leads,<br><br>Thursday 13th is branch/codefreeze day as planned [1].<br><br>Special Note:<br>Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main<br>line of defense/attack on this codefreeze. <br><br>A quick reminder what branch/codefreeze means for each component/repo owner:<br><br>0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.<br><br>1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools parent.<br> Should look something like this:<br><br><span class="Apple-tab-span" style="white-space:pre"> </span><parent><br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><groupId>org.jboss.tools</groupId><br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><artifactId>parent</artifactId><br><span class="Apple-tab-span" style="white-space:pre"> </span><span class="Apple-tab-span" style="white-space:pre"> </span><version>4.1.0.Beta2-SNAPSHOT</version><br><span class="Apple-tab-span" style="white-space:pre"> </span></parent><br><br>2) Make sure your component builds and passes its tests when run locally.<br><br> $ mvn clean verify<br><br>3) Make a branch for the Beta2 builds to use.<br><br> Most components uses master, thus the steps would be something like:<br><br> $ git checkout master<br> $ git pull origin master <br> $ git checkout -b jbosstools-4.1.0.Beta2x<br> $ git push origin jbosstools-4.1.0.Beta2x<br><br>4) Respond to this mail before end of Thursday with a "All Done for component:<br> <your component>" or "<your component> cannot branch/freeze today because of<br> <jira issues> must be done first" <br><br>Thank you!<br><br>[1] <a href="https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel">https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel</a><br><br>_______________________________________________<br>jbosstools-dev mailing list<br><a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br>_______________________________________________<br>jbosstools-dev mailing list<br>jbosstools-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br>_______________________________________________<br>jbosstools-dev mailing list<br>jbosstools-dev@lists.jboss.org<br>https://lists.jboss.org/mailman/listinfo/jbosstools-dev<br></div></blockquote></div><br></div></body></html>