[jbosstools-issues] [JBoss JIRA] (JBDS-4385) For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x

Jeff MAURY (JIRA) issues at jboss.org
Fri May 5 04:08:00 EDT 2017


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

Jeff MAURY reassigned JBDS-4385:
--------------------------------

    Assignee: Jeff MAURY


> For JBDS 10.4.0.GA: Find Missing Commits From master for jbosstools-4.4.x
> -------------------------------------------------------------------------
>
>                 Key: JBDS-4385
>                 URL: https://issues.jboss.org/browse/JBDS-4385
>             Project: Red Hat JBoss Developer Studio (devstudio)
>          Issue Type: Task
>          Components: installer
>            Reporter: Jeff MAURY
>            Assignee: Jeff MAURY
>            Priority: Blocker
>              Labels: task
>             Fix For: 10.4.0.GA
>
>
> For JBDS 10.4.0.GA: Ensure all commits pushed to master have either been made in jbosstools-4.4.x, or are intentionally excluded from jbosstools-4.4.x. 
> Below are listed all commits made to master that have not been found in jbosstools-4.4.x. It is possible these commits do exist in jbosstools-4.4.x, but the patches are not identical. It is also possible that the commits made in master are not relevant to jbosstools-4.4.x or should not be applied. 
> If there are no commits listed below, please close (do not resolve) this issue. 
> Otherwise:
>    1) Click on each link below. 
>    2) Evaluate whether the given commit *should* be in jbosstools-4.4.x
>    3) If it should be in jbosstools-4.4.x, please find out why it is not in jbosstools-4.4.x. You may need to browse jbosstools-4.4.x's commit log to find a commit that should match. 
>    4) If you cannot find a matching commit, and it *should* be committed to jbosstools-4.4.x, please cherry-pick that commit to jbosstools-4.4.x or otherwise merge it in. 
>    5) In comments, please indicate any suspicious commits (ie, commits not related to simple version changes), whether it exists in jbosstools-4.4.x, whether you have successfully merged it in now, or whether it is not intended to be committed to jbosstools-4.4.x or is inappropriate for jbosstools-4.4.x.
>    6) When all complete, please close (do not resolve) this issue.
>    
> [Search for all task JIRA|https://issues.jboss.org//issues/?jql=%28%28project+in+%28JBDS%29+and+fixVersion+%3D+%2210.4.0.GA%22%29+or+%28project+in+%28JBIDE%29+and+fixVersion+%3D+%224.4.4.Final%22%29%29+AND+labels+%3D+task]



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)


More information about the jbosstools-issues mailing list