Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [messaging-dev] [glassfish-dev] [openmq-dev] Releasing Messaging 3.1
  • From: Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx>
  • Date: Wed, 2 Mar 2022 21:18:27 +0000
  • Accept-language: en-GB, sk-SK, en-US
  • Arc-authentication-results: i=1; 1; spf=pass; dmarc=pass action=none; dkim=pass; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed;; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=EEQqhNziVaWs+wRn8Eii/ppHhmIcVzLNP/IIVgICDJs=; b=b2x1GDA0Jcy4sH7fYvwi5jXdvqbYCUJvZeNf/gBUJWzYdTRBo9QJQnXBjV6mWLu/MXxe1w5J1r1zaOQaKWNwICj7fkJ5IXR/zCxWmENPHtaTMKaReSYiFNzKN3JUpkG872w7fIEedBY9XX5PpQRN1/MQbFzPvGqd9BRlDYhwc5Bu0+NGvoE7Eled9BQX72F2es6lfdWQL+KDroysAe/RaxKI1nC2ALfRAKP5Uk9sYKTNjfhMvt+VspRaTEOs5FhTEgtXVB9JIFsCvdBGTfrMgMJekP4cFyQLPHSp3JoSZsDGBiw64XeREPAYXiFLLkBDuUWI49qyjBZ1iaDaa/bKlA==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901;; cv=none; b=hDx6PU/dtzMYLPkyXF242CoWsMzVoYpf0M9is4aLZK4HY6Epx0jp+6PJWCQno0wGz3tqgNNII6AgTWR88Mf/yT1IDJQ8P2GEYkLJIDxk28F5JgsItXYzNxIHhbBSJAyirePTbDiXrl3oQzOwqyNM+7fOI05DdVWqfcs9RfiB1hosOtrokJj4gS/YV0IeA2dtY8ezD51ZBB2FxqhQtWapcVGgKTkZS4Ly9iNqY7DEM71+cX4AdBHJeyzx1tb53IFFJIHlFzdIMkaBJ+IAp+wOgsFacFTn3ABLWEKKbdIbqUX1/tX79LjXwtJZpDxj4Nk71HJZRXywuz0ZEibQWaH7Sg==
  • Delivered-to: messaging-dev@xxxxxxxxxxx
  • List-archive: <>
  • List-help: <>
  • List-subscribe: <>, <>
  • List-unsubscribe: <>, <>
  • Suggested_attachment_session_id: 5fd878b0-eab0-c3bb-8d6c-c74eb40a0430
  • Thread-index: AQHYLm/ABm16Bukgb0Kl1GrXFMRmJ6ysly8h
  • Thread-topic: [glassfish-dev] [messaging-dev] [openmq-dev] Releasing Messaging 3.1

Hi, Piotrek,

It's good news that OpenMQ now passes the TCK! There's nothing going to be added to the TCK for Messaging 3.1, except an update to the TCK guide to align it with 3.1 version:

I saw that OpenMQ RC1 is already tagged.

Can you create a release out the RC1 tag and attach the TCK summary ( to the release?

I'd like to create a CI certification request for it so that we can finally initiate Messaging 3.1 release review. I could link the TCK summary in the Jenkins job but having it in a github release page is more persistent and credible.

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 | | info@xxxxxxxxxxx | @Payara_Fish

From: glassfish-dev <glassfish-dev-bounces@xxxxxxxxxxx> on behalf of Piotr Żygieło <piotr.zygielo@xxxxxxxxx>
Sent: 02 March 2022 20:56
To: EE4J Messaging project developer discussions <messaging-dev@xxxxxxxxxxx>
Cc: glassfish developer discussions <glassfish-dev@xxxxxxxxxxx>
Subject: Re: [glassfish-dev] [messaging-dev] [openmq-dev] Releasing Messaging 3.1
On Wed, 2 Mar 2022 at 20:30, Scott Marlow <smarlow@xxxxxxxxxx> wrote:
> So running tests again with latest should see improvment due to signature test changes merged in this morning.

Confirmed -
used newer TCK and all tests passed.

>> I think for OpenMQ to be tested for CI - it's fine to pass 904 standalone tests.
> +1 as long as all standalone tests are passing.

Seems to be doable then ;)

glassfish-dev mailing list
To unsubscribe from this list, visit

Back to the top