Re: [messaging-dev] Help/guidance with the 3.1 release needed

[arjan tijms <arjan.tijms@xxxxxxxxx>]

Hi,

The release of the actual artefacts should only be done after the ballot has concluded successfully, so for the moment jenkins is not needed.

When it's time to release, it's a matter of staging using job:

1_messaging-build-and-stage

Then when it stages correctly, run the TCK against it using job:

2_messaging-run-tck-against-staged-build

And when the TCK passes, push the staged artefacts to Maven central using job:

3_messaging-staging-to-release

On Wed, Feb 23, 2022 at 12:28 PM Ondrej Mihályi <ondrej.mihalyi@xxxxxxxxxxx> wrote:

Hi,

I'd like to proceed with the release of Messaging 3.1 and fill in the details for the release review PR: https://github.com/jakartaee/specifications/pull/455 by the end of this week (to meet the deadline for EE 10).

However, I haven't done that and I'm not familiar with how Jenkins is set up to release the new artifacts.

Can somebody help me and point me to the right direction?

I'm also on Jakarta Slack , you can contact me in the jms channel if you'd like to help me interactively. I would greatly appreciate it. I'm usually available all day since morning to late evening European time.

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

_______________________________________________
messaging-dev mailing list
messaging-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://accounts.eclipse.org