Bug 1184141
Summary: | Upgrade HornetQ to 2.3.25.Final from 2.3.24.Final-redhat-1 | ||
---|---|---|---|
Product: | [JBoss] JBoss Enterprise Application Platform 6 | Reporter: | Kabir Khan <kkhan> |
Component: | HornetQ | Assignee: | Vladimir Dosoudil <dosoudil> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Miroslav Novak <mnovak> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 6.4.0 | CC: | dosoudil, istudens, mnovak, msvehla, pcheung, pgier |
Target Milestone: | ER2 | ||
Target Release: | EAP 6.4.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-08-19 12:42:20 UTC | Type: | Component Upgrade |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 1169781, 1174152 | ||
Bug Blocks: |
Description
Kabir Khan
2015-01-20 16:20:02 UTC
release tagged: HornetQ_2_3_25_Final who's the next to be assigned in the chain for the product build? I'm adding Paul and Vladimir to cc so they're aware of this upgrade. Ok, I'm not doing my manual build this time.. will wait for a productized build.. unless someone tells me I need to upload my own build Kabir just told me I can use a community build still.. so I will do it Tag: https://github.com/hornetq/hornetq/releases/tag/HornetQ_2_3_25_Final Dev PR: https://github.com/jbossas/jboss-eap/pull/2256 MEAD build: https://brewweb.devel.redhat.com/buildinfo?buildID=417810 RPM6 wrapper: https://brewweb.devel.redhat.com/buildinfo?buildID=417813 RPM5 wrapper: https://brewweb.devel.redhat.com/buildinfo?buildID=417814 RPM7 wrapper: https://brewweb.devel.redhat.com/buildinfo?buildID=417815 Prod rebuild PR: https://github.com/jbossas/jboss-eap/pull/2257 VERIFIED with 6.4.0.ER2 *** Bug 1160614 has been marked as a duplicate of this bug. *** |