[jbosstools-issues] [JBoss JIRA] (JBIDE-20025) new commits in master branch == portlet must be upversioned

Mickael Istria (JIRA) issues at jboss.org
Thu Jun 11 01:12:02 EDT 2015


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

Mickael Istria commented on JBIDE-20025:
----------------------------------------

I'd like to add that, without reproducible qualifiers, the best practice is not even to wait for new commits to appear on master before bumping the version but directly to bump the version just after the release was branched or built, so it's always ready for new changes.

I'd also like to add that this issue happening now shows clearly that versioning troubles can happen whenever in a development stream. /cc [~dgolovin]

> new commits in master branch == portlet must be upversioned
> -----------------------------------------------------------
>
>                 Key: JBIDE-20025
>                 URL: https://issues.jboss.org/browse/JBIDE-20025
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: portal-gatein
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Snjezana Peco
>             Fix For: 4.3.0.Beta2
>
>
> [~dgolovin] reports that whenever he builds Portlet from master branch, it fails because it's got the same plugin/feature versions as the previous baseline release, but there are new commits / SHAs since that baseline.
> So, portlet should be upversioned so that the version validation test won't fail.
> cc: [~mickael_istria] [~maxandersen] [~snjeza]
> (The reason this happened is that people committed changes to a branch of code which is no longer being developed. Since not being developed, no one upversioned the code along with those commits.)
> The alternative solution to this issue is that @dgolovin should simply stop building portlet locally. We don't build it in Jenkins for the same reason. :D



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)


More information about the jbosstools-issues mailing list