[jbosstools-issues] [JBoss JIRA] (JBIDE-13577) refactor & clean up jbosstools-target-platforms repo

[Mickael Istria (JIRA)]

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

Mickael Istria commented on JBIDE-13577:
----------------------------------------

[~maxandersen] did clean the "big binary" so the jbosstools-target-platfrom repo is now a few seconds to clone.
I've renamed branches, except I did not move 4.3.0 to master, but to 4.30.x. "master" currently contains some common stuff, we need to decide where to put it before changing master.
Also, CI jobs assume that the branch name is related the version, and extract some info from that. It's nice. Useless "master" removes such informations and forces us to make some manual maintenance based on conventions to remember. Is it really better?
                
> refactor & clean up jbosstools-target-platforms repo
> ----------------------------------------------------
>
>                 Key: JBIDE-13577
>                 URL: https://issues.jboss.org/browse/JBIDE-13577
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: target-platform
>    Affects Versions: 4.0.0.Final, 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>            Reporter: Nick Boldt
>            Assignee: Mickael Istria
>             Fix For: 4.0.0.Final, 4.0.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2
>
>
> Rename branches as follows:
> 4.2.0 -> 4.20.x (currently contains 4.20.6)
> 4.2.1 -> 4.21.x (currently contains 4.21.4)
> (new) -> 4.22.x (soon will contain  4.22.0)
> 4.3.0 -> master (currently contains 4.30.3)
> Also, purge any large binaries that are causing the repo to be >50M in size.
> When Kepler R is released (Eclipse 4.3.0.Final) we can branch a 4.30.x branch and work on the new 4.31.x target platforms (Kepler SR1) in the master branch.

--
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