Finalize the Jakarta Messaging 3.1 Release

jeanouii commented 2 years ago

Please complete these steps to finalize the release:

[ ] promotes api staging release promotes the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
[ ] go through the merged jakarta.ee specification website page to verify all the links are valid.
[ ] if XML Schemas are published on https://jakarta.ee/schemas, send a PR to update the status from Draft to Final.
[ ] approve the compatibility request.
[ ] The compatible implementation project/vendor MUST send an email to tck@eclipse.org for approval of the compatible implementation for trademark usage.
[ ] merge any final release branch as appropriate for the branch management for the project.

pzygielo commented 2 years ago

Hello Messaging Team,

May I ask to have api artifact released to Central, please?

OndroMih commented 2 years ago

Hi @pzygielo, it's released now: https://repo.maven.apache.org/maven2/jakarta/jms/jakarta.jms-api/3.1.0/

pzygielo commented 2 years ago

:tada: - @OndroMih - thank you!

OndroMih commented 1 year ago

3.1.0 is released, closing this issue.

pzygielo commented 1 year ago

All projects seem to be at 3.1.0-SNAPSHOT on master. So the branch that 3.1.0 was released from was not merged to master, was it? ~It also doesn't look like being pushed here.~ ~edit: it was here pointing to 0425a22 but it's gone now.~ apparently I'm blind - 3.1.0 is there

OndroMih commented 1 year ago

You're right, 3.1.0 wasn't merged to master yet. Jenkins was used to release in a separate branch, so the release branch and tag exist.

pzygielo commented 4 weeks ago

https://www.eclipse.org/lists/messaging-dev/msg00088.html

OndroMih commented 3 weeks ago

The master branch is now up to date: https://github.com/jakartaee/messaging/pull/339

jakartaee / messaging

Finalize the Jakarta Messaging 3.1 Release #323

Please complete these steps to finalize the release: