[messaging-dev] Releasing Messaging 3.1

[Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx>]

Hi all,

I'm trying to release Messaging 3.1 this week and I realized there's no email thread dedicated to this so I'm starting this thread to keep information about the progress in one place for everybody involved.

Current status:

Messaging 3.1 API:

• API artifact 3.1.0 staged in Eclipse Nexus repository (no parent artifact anymore, currently no known issues with the artifact)
• I've raised the release review PR with details for the review committee: https://github.com/jakartaee/specifications/pull/455
• I've created a CI request for GlassFish (https://github.com/jakartaee/messaging/issues/321) - this was probably a bit premature because everything isn't in place but I wanted to track the implementation status. It's enough to have OpenMQ as the CI, so, in the end, maybe we'll change the CI request to use OpenMQ or create another request for OpenMQ
  

Messaging 3.1 TCK

• Part of the Jakarta EE TCK
• The TCK is regularly executed against GlassFish/OpenMQ in this Jenkins job
• The tests modified to cover all the new functionality (only repeatable annotations)
  
• The signature tests updated
  
• The metadata tests updated
  
• The standalone TCK guide still mentions 3.0 version, needs to be fixed (I plan to fix it today)
• The latest TCK run failed on signature tests and metadata tests

OpenMQ

• Upgraded Messaging to 3.1 (https://github.com/eclipse-ee4j/openmq/pull/1398)
• this should pass the signature tests
  
• I think that the JMS metadata still needs to be updated for ConnectionMetaData (I think in the ConnectionMetaDataAdapter)
• this should then pass all the metadata tests
• A new version of OpenMQ should be released to act as a CI for Messaging

GlassFish

• Currently, the only role of GlassFish is to act as the CI because I think that the TCK Jenkins job runs against the OpenMQ bundled in GlassFish. If we can pass the TCK with plain OpenMQ, then we don't need GlassFish for releasing Messaging 3.1
• Upgraded Messaging API to 3.1
• Needs to upgrade OpenMQ after a new OpenMQ version is released
  

OpenMQ and GlassFish teams, please, can you provide the status from your side and share your plans towards passing the Messaging 3.1 TCK?

Kind regards,

Ondrej Mihályi

Senior Payara Service Engineer
Payara - Supported Enterprise Software for Jakarta EE and MicroProfile Applications
US: +1 415 523 0175 | UK: +44 207 754 0481

----------------------------------------------------------------------------------------------------------------------

Payara is a proud recipient of the prestigious Queen's Award for Enterprise: International Trade 2021

Payara-Tech LDA, Registered Office: Rua Nova de São Pedro no. 54, 2nd floor, room “D”, 9000 048 Funchal, Ilha da Madeira, Portugal

VAT: PT 515158674 | www.payara.fish | info@xxxxxxxxxxx | @Payara_Fish