Nick Boldt created JBIDE-17763: ---------------------------------- Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Forge] Key: JBIDE-17763 URL: https://issues.jboss.org/browse/JBIDE-17763 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: forge Reporter: Nick Boldt Priority: Blocker For JBIDE 4.2.0.Beta3 [Forge]: Please perform the following tasks: 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*. Otherwise: 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3 [Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...] 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1. *NOTE:* If you already did this for the previous milestone you do *not* need to do so again. {code} mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT {code} 2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT; {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.2.0.Beta3-SNAPSHOT</version> </parent> {code} 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT; {code} mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) or mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged) {code} 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch; {code} git checkout master git pull origin master git checkout -b jbosstools-4.2.0.Beta3x git push origin jbosstools-4.2.0.Beta3x {code} 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*. {code} git checkout master git pull origin master {code} 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*: {code} <parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.2.0.Beta3-SNAPSHOT</version> </parent> {code} Now, your root pom will use parent pom version: * *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and * *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch. 7. Close (do not resolve) this JIRA when done. 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next. [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Forge task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.2.6#6264)