[jbosstools-issues] [JBoss JIRA] (JBIDE-18468) For JBIDE 4.2.0.CR2: Prepare for CR2 release [JBT Update Sites]

[Nick Boldt (JIRA)]

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

Nick Boldt closed JBIDE-18468.
------------------------------
      Assignee: Nick Boldt
    Resolution: Done


> For JBIDE 4.2.0.CR2: Prepare for CR2 release [JBT Update Sites]
> ---------------------------------------------------------------
>
>                 Key: JBIDE-18468
>                 URL: https://issues.jboss.org/browse/JBIDE-18468
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: updatesite
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.2.0.CR2
>
>
> For JBIDE 4.2.0.CR2 [JBT Update Sites]: Please perform the following tasks:
> 0. If nothing has changed in your component since JBT 4.2.0.CR1 or JBDS 8.0.0.CR1 (eg., XulRunner, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise, for all other projects:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2 or 8.0.0.GA. Unresolved issues should be marked with a *respin-* label, unless they are issues which cannot be completed until closer to GA.
> [Unresolved JIRAs with fixVersion = 4.2.0.CR2, 4.2.0.Final, 8.0.0.CR2, 8.0.0.GA|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%28%224.2.0.CR2%22%2C%20%224.2.0.Final%22%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%28%228.0.0.CR2%22%2C%228.0.0.GA%22%29%29%29%20and%20resolution%20%3D%20Unresolved]
> 1. In the *{color:blue}jbosstools-4.2.x{color}* branch, update your root pom to use parent pom version *{color:blue}4.2.0.CR2-SNAPSHOT{color}*
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.2.0.CR2-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.40.0.CR2-SNAPSHOT
> mvn clean verify -Dtpc.version=4.41.0.CR2-SNAPSHOT
> {code}
> 5. If you did not already do so, *{color:orange}IN YOUR 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.3.0.Alpha1-SNAPSHOT{color}*:
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.3.0.Alpha1-SNAPSHOT</version>
>   </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.3.0.Alpha1-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 4. 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.CR2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.2.0.CR2%22%29%29+AND+labels+%3D+task], or [Search for JBT Update Sites task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%228.0.0.CR2%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.2.0.CR2%22%29%29+AND+labels+%3D+task+and+component+in+%28%22updatesite%22%29]



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)