[jbosstools-issues] [JBoss JIRA] (JBIDE-16455) For JBIDE 4.2.0.Alpha2: Code Freeze + Branch [Base]

Alexey Kazakov (JIRA) issues at jboss.org
Thu Feb 6 14:38:28 EST 2014


     [ https://issues.jboss.org/browse/JBIDE-16455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexey Kazakov resolved JBIDE-16455.
------------------------------------

    Resolution: Done

    
> For JBIDE 4.2.0.Alpha2: Code Freeze + Branch [Base]
> ---------------------------------------------------
>
>                 Key: JBIDE-16455
>                 URL: https://issues.jboss.org/browse/JBIDE-16455
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: common/jst/core, usage
>            Reporter: Nick Boldt
>            Assignee: Alexey Kazakov
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.2.0.Alpha2
>
>
> For JBIDE 4.2.0.Alpha2 [Base]: 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.Alpha2
> [Unresolved JIRAs with fixVersion = 4.2.0.Alpha2, 8.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%28%224.2.0.Alpha2%22%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%28%228.0.0.Alpha2%22%29%29%29%20and%20resolution%20%3D%20Unresolved]
> 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.Alpha2-SNAPSHOT; 
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.2.0.Alpha2-SNAPSHOT</version>
>   </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Alpha2;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.Alpha2  # (if the TP is already released)
>   or
> mvn clean verify -Dtpc.version=4.40.0.Alpha2-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new jbosstools-4.2.0.Alpha2x branch; 
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.2.0.Alpha2x
> git push origin jbosstools-4.2.0.Alpha2x
> {code}
> 5. Close (do not resolve) this JIRA when done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%228.0.0.Alpha2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.2.0.Alpha2%22%29%29+AND+labels+%3D+task], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%228.0.0.Alpha2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.2.0.Alpha2%22%29%29+AND+labels+%3D+task+and+component+in+%28%22usage%22%2C%22common%2Fjst%2Fcore%22%29]

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jbosstools-issues mailing list