Re: [jbosstools-dev] ACTION REQUIRED: core Beta2 branch/codefreeze Thursday - steps inside
ALL DONE for OpenShift. See Details below:
0) DONE
1) DONE
2) DONE
[INFO] openshift.all ..................................... SUCCESS [0.585s]
[INFO] openshift.plugins ................................. SUCCESS [0.013s]
[INFO] org.jboss.tools.openshift.egit.core ............... SUCCESS [2.417s]
[INFO] org.jboss.tools.openshift.egit.ui ................. SUCCESS [0.553s]
[INFO] org.jboss.tools.openshift.express.client .......... SUCCESS [0.508s]
[INFO] org.jboss.tools.openshift.express.ui .............. SUCCESS [5.324s]
[INFO] openshift.tests ................................... SUCCESS [0.006s]
[INFO] org.jboss.tools.openshift.egit.test ............... SUCCESS [23.883s]
[INFO] org.jboss.tools.openshift.express.test ............ SUCCESS [30.976s]
[INFO] openshift.features ................................ SUCCESS [0.009s]
[INFO] org.jboss.tools.openshift.egit.integration.feature SUCCESS [0.287s]
[INFO] org.jboss.tools.openshift.express.feature ......... SUCCESS [0.249s]
[INFO] org.jboss.tools.openshift.egit.integration.test.feature SUCCESS
[0.137s]
[INFO] org.jboss.tools.openshift.express.test.feature .... SUCCESS [0.149s]
[INFO] openshift.site .................................... SUCCESS [13.779s]
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 11:20.463s
[INFO] Finished at: Thu Jun 13 21:07:28 CEST 2013
3) DONE
To git@github.com:jbosstools/jbosstools-openshift.git
* [new branch] jbosstools-4.1.0.Beta2x -> jbosstools-4.1.0.Beta2x
On 06/11/2013 04:12 PM, Max Rydahl Andersen wrote:
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.plug...
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev