]
Nick Boldt updated JBDS-3843:
-----------------------------
Sprint: devex #6 April 2016
For JBDS 10.0.0.Alpha1: Find Missing Commits From jbosstools-4.3.x
for master
-----------------------------------------------------------------------------
Key: JBDS-3843
URL:
https://issues.jboss.org/browse/JBDS-3843
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Rob Stryker
Assignee: Denis Golovin
Priority: Blocker
Labels: task
Fix For: 10.0.0.Alpha1
For JBDS 10.0.0.Alpha1: Ensure all commits pushed to jbosstools-4.3.x have either been
made in master, or are intentionally excluded from master.
Below are listed all commits made to jbosstools-4.3.x that have not been found in master.
It is possible these commits do exist in master, but the patches are not identical. It is
also possible that the commits made in jbosstools-4.3.x are not relevant to master 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 master
3) If it should be in master, please find out why it is not in master. You may need to
browse master's commit log to find a commit that should match.
4) If you cannot find a matching commit, and it *should* be committed to master,
please cherry-pick that commit to master 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 master, whether you have successfully merged
it in now, or whether it is not intended to be committed to master or is inappropriate for
master.
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+an...]