[jbosstools-issues] [JBoss JIRA] (JBIDE-19951) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]

[Martin Malina (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13075271#comment-13075271 ] 

Martin Malina commented on JBIDE-19951:
---------------------------------------

Beta1x branch has been created here:
https://github.com/jbosstools/jbosstools-integration-tests/tree/jbosstools-4.3.0.Beta1x

PR to move master to 4.3.0.Beta2-SNAPSHOT parent pom is here:
https://github.com/jbosstools/jbosstools-integration-tests/pull/997

[~nickboldt] do you think I also need to upversion our plugins now? In the past we only did it when we moved to the next version of JBoss Tools, e.g. from 4.2.x to 4.3.x. Please let me know.

> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [integration-tests]
> ---------------------------------------------------------------
>
>                 Key: JBIDE-19951
>                 URL: https://issues.jboss.org/browse/JBIDE-19951
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: qa
>            Reporter: Nick Boldt
>            Assignee: Martin Malina
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Central Discovery]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*. 
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22JBIDE%22%20and%20fixVersion%20in%20%28%224.3.0.Beta1%22%29%29%20or%20%28project%20%3D%20%22JBDS%22%20and%20fixversion%20in%20%28%229.0.0.Beta1%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.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch. 
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT; 
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.3.0.Beta1-SNAPSHOT</version>
>   </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT  # (if the TP is still a SNAPSHOT)
>   or
> mvn clean verify -Dtpc.version=4.50.0.Beta1           # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch; 
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {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.3.0.Beta2-SNAPSHOT{color}*:
> {code}
>   <parent>
>     <groupId>org.jboss.tools</groupId>
>     <artifactId>parent</artifactId>
>     <version>4.3.0.Beta2-SNAPSHOT</version>
>   </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 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%29%20and%20fixVersion%20%3D%20%229.0.0.Beta1%22%29%20or%20%28project%20in%20%28JBIDE%29%20and%20fixVersion%20%3D%20%224.3.0.Beta1%22%29%29%20AND%20%28labels%20%3D%20new_and_noteworthy%20OR%20summary%20~%20%22New%20and%20Noteworthy%20for%204.3.0.Beta1%22%29%20AND%20resolution%20is%20null] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Beta1%22%29%29+AND+labels+%3D+task], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%229.0.0.Beta1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.3.0.Beta1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22discovery%22%29]



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)