[jbosstools-issues] [JBoss JIRA] (JBIDE-23159) Bump plugin/feature/component versions in main branch when creating branches for Final/GA release

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-23159:
------------------------------------

With the advent of the baseline comparison check from [~mickael_istria] and the fact that we now have jgit timestamps, IMHO we don't have to force projects or subprojects to upversion for every jbosstools-a.b.c.x branchpoint.

When we DO move to a new version of Eclipse and branch to a.b.x (eg., 4.4.x) then we definitely have to move SOME things up, but again, it can be done on a case-by-case basis since we have jgit timestamps and baseline check.

[~mickael_istria] would you agree?

> Bump plugin/feature/component versions in main branch when creating branches for Final/GA release 
> --------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-23159
>                 URL: https://issues.jboss.org/browse/JBIDE-23159
>             Project: Tools (JBoss Tools)
>          Issue Type: Sub-task
>          Components: build
>            Reporter: Alexey Kazakov
>            Assignee: Nick Boldt
>             Fix For: 4.4.2.AM1
>
>
> The script which creates branches for a Final/GA release when codefreezing should also bump plugin/feature/component versions in main branch (master or maintenance).
> The script should probably have a parameter which tells what segment of the version we want to increment: X.Y.Z



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)