[jbosstools-issues] [JBoss JIRA] (JBIDE-15963) For JBIDE 4.1.1.CR1: Code Freeze + Branch [Portlet]

Snjezana Peco (JIRA) jira-events at lists.jboss.org
Thu Nov 14 06:23:07 EST 2013


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

Snjezana Peco reassigned JBIDE-15963:
-------------------------------------

    Assignee: Snjezana Peco

    
> For JBIDE 4.1.1.CR1: Code Freeze + Branch [Portlet]
> ---------------------------------------------------
>
>                 Key: JBIDE-15963
>                 URL: https://issues.jboss.org/browse/JBIDE-15963
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: portal-gatein
>            Reporter: Nick Boldt
>            Assignee: Snjezana Peco
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.1.1.CR1
>
>
> For JBIDE 4.1.1.CR1 [Portlet]: Please perform the following tasks:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.1.1.CR1
> 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.1.1.CR1-SNAPSHOT; 
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.1.1.CR1-SNAPSHOT</version>
>   </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform versions;
> {code}
> mvn clean verify -Dtpc.version=4.31.0.Final
> mvn clean verify -Dtpc.version=4.31.1.Alpha2-SNAPSHOT # (if still being staged)
> {code}
> or{code}
> mvn clean verify -Dtpc.version=4.31.0.Final
> mvn clean verify -Dtpc.version=4.31.1.Alpha2 # (if released)
> {code}
> 4. Branch from your existing jbosstools-4.1.x branch into a new *jbosstools-4.1.1.x* (not CR1x) branch; 
> {code}
> git checkout jbosstools-4.1.x
> git pull origin jbosstools-4.1.x
> git checkout -b jbosstools-4.1.1.x
> git push origin jbosstools-4.1.1.x
> {code}
> 5. Close (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+%227.1.0.CR1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.CR1%22%29%29+AND+labels+%3D+task], or [Search for Portlet task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%227.1.0.CR1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.CR1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22portal-gatein%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