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

[Max Rydahl Andersen]

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