[jbosstools-issues] [JBoss JIRA] (JBIDE-14642) How to automate process of bumping version for changed modules/submodules for every release

[Denis Golovin (JIRA)]

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

Denis Golovin commented on JBIDE-14642:
---------------------------------------

First lets explain how we do that manually and then figure out what can be automated and how. 

AFAIK it is important to update version after maintenance branch was created and module/submodule got firs commit into master.  Then when update is needed we should follow Eclipse rules and decide what part of the version should be updated. Then whole module/submodule gets updated using tycho version update plugin. Then it stays with this version till next release.

Questions:
* Any commit should be counted? What if commit was merged in both branches maintenance and master?
* What if only pom.xml was updated in some way that doesn't affect deliverables?
                
> How to automate process of bumping version for changed modules/submodules for every release
> -------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-14642
>                 URL: https://issues.jboss.org/browse/JBIDE-14642
>             Project: Tools (JBoss Tools)
>          Issue Type: Task
>          Components: Build/Releng
>    Affects Versions: 4.1.0.Beta1
>            Reporter: Denis Golovin
>            Assignee: Max Rydahl Andersen
>             Fix For: 4.2.0.Alpha1
>
>
> The versions of plugins are constantly discovered to not be uptodated when they should and things like Usage and others where it is critical are not getting bumped.
> We need two things:
> A) detect when versions are not bumped properly - we got parts of this in various places, but they are not run nor documented regularly (having a green build verifying versions are not conflicting would be a Good Thing)
> B) document/automate a process which every affected lead can follow to make this happen and if not See #A

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