[jbosstools-issues] [JBoss JIRA] (JBIDE-15438) For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear]

Nick Boldt (JIRA) jira-events at lists.jboss.org
Sat Sep 7 17:27:03 EDT 2013


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

Nick Boldt commented on JBIDE-15438:
------------------------------------

Spinning:

https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-aerogear_41/ >=38
                
> For JBIDE 4.1.1.Alpha1: Code Freeze + Branch [Aerogear]
> -------------------------------------------------------
>
>                 Key: JBIDE-15438
>                 URL: https://issues.jboss.org/browse/JBIDE-15438
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: aerogear-hybrid
>            Reporter: Nick Boldt
>            Assignee: Gorkem Ercan
>            Priority: Blocker
>              Labels: task
>             Fix For: 4.1.1.Alpha1
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> For JBIDE 4.1.1.Alpha1: Please perform the following tasks:
> 0. If nothing has changed in your component since the least GA release on this branch, *Reject this JIRA*.
> Otherwise:
> 0) Make sure your component(s) has no remaining jiras for 4.1.1.Alpha1 in jira.
> 1) Make sure you component(s) version number has changed micro version if it had changes since 4.1.0 was released!
>    
>    You can use this to change it for a subtree:
>   {code} mvn org.eclipse.tycho:tycho-versions-plugin:set-version -DnewVersion=<component-version>-SNAPSHOT{code}
> 2) Make sure your component uses 4.1.1.Alpha1-SNAPSHOT as the version for jboss tools parent.
>    Should look something like this:
> {code}
>         <parent>
>                 <groupId>org.jboss.tools</groupId>
>                 <artifactId>parent</artifactId>
>                 <version>4.1.1.Alpha1-SNAPSHOT</version>
>         </parent>{code}
> 3) Make sure your component builds and passes its tests when run locally.
>    {code}$ mvn clean verify -Dtpc.version=4.31.0.Alpha1{code}
> 4) Make a branch for the Alpha1 builds to use.
>    This would be made on jbosstools-4.1.x, thus the steps would be something like:
> {code}   $ git checkout jbosstools-4.1.x
>    $ git pull origin jbosstools-4.1.x
>    $ git checkout -b jbosstools-4.1.1.Alpha1x
>    $ git push origin jbosstools-4.1.1.Alpha1x{code}
> 5) Resolve the jira related to branching for your component or comment on it why it can not be done.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%227.1.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.Alpha1%22%29%29+AND+labels+%3D+task], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%227.1.0.Alpha1%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.1.1.Alpha1%22%29%29+AND+labels+%3D+task+and+component+in+%28%22aerogear-hybrid%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