[jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside

[Brian Fitzpatrick]

Thanks to some help from Denis, WS tests are now blue! 

Thanks Denis!

Still hoping for some help from Rob Stryker on the ESB test failures.

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat

----- Original Message -----
From: "Brian Fitzpatrick" <bfitzpat at redhat.com>
To: "Max Rydahl Andersen" <manderse at redhat.com>
Cc: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
Sent: Thursday, June 13, 2013 2:32:21 PM
Subject: Re: [jbosstools-dev] ACTION REQUIRED: core Beta2	branch/codefreeze	Thursday - steps inside

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.

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)

So unfortunately ESB & WS are not going to be ready for code freeze because of these two test issues.

_______________________________
Brian Fitzpatrick (aka "Fitz")
Senior Software Engineer, SOA-P
JBoss by Red Hat

----- Original Message -----
From: "Max Rydahl Andersen" <manderse at redhat.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev at lists.jboss.org>
Sent: Tuesday, June 11, 2013 8:12:35 AM
Subject: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze	Thursday - steps inside

Hi core-compnent leads,

Thursday 13th is branch/codefreeze day as planned [1].

Special Note:
Nick and I is at JUDCon/Red Hat summit so Michael and Denis is the main
line of defense/attack on this codefreeze. 

A quick reminder what branch/codefreeze means for each component/repo owner:

0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta2 in jira.
   
1) Make sure your component uses 4.1.0.Beta2-SNAPSHOT as the version for jboss tools parent.
   Should look something like this:
 
	<parent>
		<groupId>org.jboss.tools</groupId>
		<artifactId>parent</artifactId>
		<version>4.1.0.Beta2-SNAPSHOT</version>
	</parent>

2) Make sure your component builds and passes its tests when run locally.

   $ mvn clean verify

3) Make a branch for the Beta2 builds to use.

   Most components uses master, thus the steps would be something like:

   $ git checkout master
   $ git pull origin master 
   $ git checkout -b jbosstools-4.1.0.Beta2x
   $ git push origin jbosstools-4.1.0.Beta2x

4) Respond to this mail before end of Thursday with a "All Done for component:
   <your component>" or "<your component> cannot branch/freeze today because of
   <jira issues> must be done first" 

Thank you!

[1] https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plugin.system.project%3Aversions-panel

_______________________________________________
jbosstools-dev mailing list
jbosstools-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev