Re: [jbosstools-dev] ACTION REQUIRED: Beta1 branch/codefreeze today - steps inside

Looks we go them all with the last pushes that branched: jbosstools-hibernate,jbosstools-arquillian,jbosstools-birt, jbosstools-portlet. Thanks - nick, over to you. /max On Fri, May 17, 2013 at 01:01:49PM +0200, Max Rydahl Andersen wrote: > Hi all, > > Today is branch/codefreeze day as planned [1]. > > Special note: > Newcomers to this came is jbosstools-arquillian and > jbosstools-aerogear - Snjezan/Gorkem, speak up if any issues doing > this. > > A quick reminder what that means for each component/repo owner: > > 0) Make sure your component(s) has no remaining jiras for 4.1.0.Beta1 in jira. > > If anything left over (besides New and noteworthy writing issues) that would > be done in respins which we wish to keep to a bare minimum, hopefully > completely avoid. > 1) Make sure your component uses 4.1.0.Beta1-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.Beta1-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 beta1 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.Beta1x > $ git push origin jbosstools-4.1.0.Beta1x > > 4) Respond to this mail before end of today 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