[
https://issues.jboss.org/browse/EMBJOPR-362?page=com.atlassian.jira.plugi...
]
Larry O'Leary commented on EMBJOPR-362:
---------------------------------------
We probably have 4 to 6 weeks before EAP 5.1.2 will be at a point that we will need to get
all changes finalized. My biggest concern is that in addition to the two dependent bugs
linked to this JIRA, there are around 30 more that we need to get brought in. I plan to
work with ccrouch over the next week or two to get those bugs identified and log them in
JIRA so they can be captured in the admin-console release notes.
Tag SP5 release on 1.3.4 for inclusion in EAP 5.1.2
---------------------------------------------------
Key: EMBJOPR-362
URL:
https://issues.jboss.org/browse/EMBJOPR-362
Project: Embedded Jopr
Issue Type: Release
Affects Versions: 1.3.4
Reporter: Larry O'Leary
Priority: Blocker
Labels: release
Fix For: 1.3.4
There are a few issues that affect admin-console in EAP 5 that have been addressed since
the release of EAP 5.0.1, EAP 5.1, and EAP 5.1.1. We need to get these fixes pushed into
admin-console for EAP 5.1.2. This will require a new tag on the 1.3.4 release branch.
Currently, EAP 5.1.1 is using Embedded JOPR 1.3.4.SP4. We need to get the appropriate
fixes committed to the Embedded JOPR branch and the tag created (1.3.4.SP5) and get the
tag into the downstream EAP 5.1 CP branch being tracked by JBPAPP-6766
--
This message is automatically generated by JIRA.
For more information on JIRA, see:
http://www.atlassian.com/software/jira