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

[Nick Boldt (JIRA)]

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

Nick Boldt closed JBIDE-13577.
------------------------------

    Resolution: Done


Explain to me how having a "publish" branch would be the same as all the other projects which do not have a "publish" branch? Or how having a .x branch for JBT 3.2.x, 3.3.x, 4.0.x, and soon 4.1.x is so different from having TPs with branches called 4.20.x, 4.21.x, 4.22.x, and 4.30.x? 

.x branches in projects.
.x branches in target platform project. 

Seems pretty similar. :D

----

As to moving a single shell script which is ONLY useful in the context of target platforms to the build-ci repo where I'll have to rename it so it doesn't collide name-wise with the OTHER publish.sh script (used by all the projects, so it makes sense as a shared/common script), and making me update Jenkins jobs to pull from a different raw.github URL... yes, that sounds logical. 

Please open a new jira for that bit of arbitrary make-work.
                
> 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.1.Final, 4.1.0.Alpha1, 4.1.0.Alpha2, 4.0.0.Final
>
>
> 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