Re: [jbosstools-dev] ACTION: codefreeze for 4.1.1.Alpha1

Max, I verified what I could and it seems we're done with codefreeze. Here is the list of components I checked including version update: JBoss Tools jbosstools-aerogear no changes jbosstools-arquillian 1.0.4-SNAPSHOT => 1.0.5-SNAPSHOT jbosstools-base/common 3.5.1-SNAPSHOT => 3.5.2-SNAPSHOT jbosstools-base/foundation 1.0.0-SNAPSHOT => 1.0.1-SNAPSHOT jbosstools-base/runtime no changes jbosstools-base/stacks no changes jbosstools-base/tests no changes jbosstools-base/usage no cahnges jbosstools-birt no changes jbosstools-central/central 1.2.0-SNAPSHOT => 1.2.1-SNAPSHOT jbosstools-central/examples 1.5.0-SNAPSHOT => 1.5.1-SNAPSHOT jbosstools-central/maven 1.5.0-SNAPSHOT => 1.5.1-SNAPSHOT jbosstools-forge no changes jbosstools-freemarker no changes jbosstools-gwt no changes jbosstools-hibernate no changes jbosstools-javaee/cdi no changes jbosstools-javaee/jsf 3.5.0-SNAPSHOt => 3.5.1-SNAPSHOT jbosstools-javaee/seam no changes jbosstools-jst 3.5.0-SNAPSHOT => 3.5.1-SNAPSHOT jbosstools-livereload 1.0.0-SNAPSHOT => 1.1.0-SNAPSHOT jbosstools-openshift 2.5.0-SNAPSHOT => 2.5.1-SNAPSHOT jbosstools-portlet no changes jbosstools-server/archives 3.4.100-SNAPSHOT => 3.4.101-SNAPSHOT jbosstools-server/as 2.4.100-SNAPSHOT => 2.4.101-SNAPSHOT jbosstools-server/jmx 1.4.0-SNAPSHOT => 1.4.1-SNAPSHOT jbosstools-server/wtp 1.0.0-SNAPSHOT => 1.0.1-SNAPSHOT jbosstools-vpe 3.5.0-SNAPSHOT => 3.5.1-SNAPSHOT jbosstools-webservices 1.5.0-SNAPSHOT => 1.5.1-SNAPSHOT JBoss Developer Studio jbdevstudio-product 7.0.0-SNAPSHOT => 7.1.0-SNAPSHOT Denis On 09/05/2013 09:13 AM, Max Rydahl Andersen wrote: > Hi all, > > Today is branch/codefreeze day as planned for jbosstools-4.1.1.Alpha1 [1]. > > Special note: > A. This only involves projects that are included in JBoss Tools Core/Developer Studio, it is *not* related > to things that are part of JBoss Tools Integration Stack (i.e. bpel, esb, jbpm3, etc.) > > B. This is an alpha, mainly to pick up Kepler SR1 fixes and already done bugfixes/features. > There is no respins or QE planned for this besides "does it install" test. > > By request jiras for each component have been created too: see https://issues.jboss.org/browse/JBIDE-15437 and subtasks. > > These jiras contains similar but less details as the instructions below: > > 0) Make sure your component(s) has no remaining jiras for 4.1.1.Alpha1 in jira. > > 1) Make sure you component(s) version number has changed micro version if it had changes since 4.1.0 was released! > > You can use this to change it for a subtree: > > mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<component-version>-SNAPSHOT > > 2) Make sure your component uses 4.1.1.Alpha1-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.1.Alpha1-SNAPSHOT</version> > </parent> > > 3) Make sure your component builds and passes its tests when run locally. > > $ mvn clean verify -Dtpc.version=4.31.0.Alpha1 > > 4) Make a branch for the Alpha1 builds to use. > > This would be made on jbosstools-4.1.x, thus the steps would be something like: > > $ git checkout jbosstools-4.1.x > $ git pull origin jbosstools-4.1.x > $ git checkout -b jbosstools-4.1.1.Alpha1x > $ git push origin jbosstools-4.1.1.Alpha1x > > 5) Resolve the jira related to branching for your component or comment on it why it can not be done. > > 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