[embjopr-issues] [JBoss JIRA] Commented: (EMBJOPR-362) Tag SP5 release on 1.3.4 for inclusion in EAP 5.1.2

[Ian Springer (JIRA)]

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

Ian Springer commented on EMBJOPR-362:
--------------------------------------

The process for the admin-console release should be:

1) Tag RHQ 3.0.0.EmbJopr4 off http://git.fedorahosted.org/git/?p=rhq/rhq.git;a=shortlog;h=refs/heads/AdminConsole_EAP_5_1
2) Tag EmbJopr 1.3.4.SP5 off https://svn.jboss.org/repos/embjopr/branches/AdminConsole_EAP_5_1 after updating its root pom to depend on RHQ 3.0.0.EmbJopr4

Larry, when do we need this by?


> 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