[
https://issues.jboss.org/browse/JBIDE-15312?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-15312:
-------------------------------------
The previous comment is incorrect. Maintenance should not be pushed to 2.4.200. 2.4.200
would be if master expected no changes except for 1 line fixes. Maintenance should be
pushed to 2.4.101. Master will not take 2.4.200 because it is obvious that large changes
are afoot.
TODO:
MAINTENANCE
- archives: from 3.4.0 to 3.4.1
- as: from 2.4.100 to 2.4.101
- jmx: from 1.4.0 to 1.4.1
- wtp: from 1.0.0 to 1.0.1
MASTER
- archives: from 3.4.0 to 3.5.0
- as: from 2.4.100 to 2.5.0
- jmx: from 1.4.0 to 1.5.0
- wtp: from 1.0.0 to 1.1.0
To be honest, I do feel that master for archives, jmx, and wtp should be pushed to
3.4.100, 1.4.100, and 1.0.100 respectively. In order to avoid mistakes like we had for
this release, I would need to open jiras NOW targeted to final to revisit the version
ranges. But I am also ok accepting the minor bump instead, as it is less likely to cause
problems.
Update all AS versions AND manifest.mf dependency version ranges
-----------------------------------------------------------------
Key: JBIDE-15312
URL:
https://issues.jboss.org/browse/JBIDE-15312
Project: Tools (JBoss Tools)
Issue Type: Task
Components: server
Affects Versions: 4.1.0.Final
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.1.1.Final, 4.2.0.Alpha1
API has been added in both branch and master. THis requires an update of version ranges.
--
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