Tracking issue for final JMS integration. Any show-stopper bugs will be linked to this issue. As of this date, the only change planned is to bump the revision to 2.0. Corresponding maven artifacts as well as RI binary and source bundles will be created from this build.
Information for the 4.0 bug review process:
What is the impact on the customer of the bug?
Should be minimal if no other issues are attached.
How likely is it that a customer will see the bug and how serious is the bug?
Is it a regression? Does it meet other bug fix criteria (security, performance, etc.)?
What CTS failures are caused by this bug?
Required to bring the API serial ID to 2.0
What is the cost/risk of fixing the bug?
Minimal. Tests have already been performed to assure this build will complete as planned.
Is there an impact on documentation or message strings?
Which tests should QA (re)run to verify the fix did not destabilize GlassFish?
MQ QA will verify, prior to final integration into GlassFish RI / 4.0
Which is the targeted build of 4.0 for this fix?
Build 86 (RC2)