Jakarta Messaging 3.0 Specification Release Review was successful -- Final checklist items

[edbratt]

Jakarta Messaging 3.0 release ballot has completed and has been accepted. Congratulations and thank you for your contributions so far. Please perform the following actions to finalize and finish this release.

• [x] promote api staging release; promote the specification api jars to maven central. An example release job script can be found here https://wiki.eclipse.org/MavenReleaseScript.
• [x] go through the merged jakarta.ee specification website page to verify all the links are valid.
• [x] approve the compatibility request.
• [x] The compatible implementation project/vendor MUST send an email to tck@eclipse.org for approval of the compatible implementation for trademark usage.
• [x] merge any final release branch as appropriate for the branch management for the project.

[dblevins]

I'll let someone from Open MQ execute "The compatible implementation project/vendor MUST send an email to tck@eclipse.org for approval of the compatible implementation for trademark usage."

[arjantijms]

I just sent the mail, cc'ing @dblevins

[arjantijms]

At the moment https://jakarta.ee/specifications/messaging/3.0/ still points to the milestone, but this typically takes some time to be updated.

[arjantijms]

Verified jars are in maven central: https://repo1.maven.org/maven2/jakarta/jms/jakarta.jms-api/3.0.0/

[edbratt]

At the moment https://jakarta.ee/specifications/messaging/3.0/ still points to the milestone, but this typically takes some time to be updated.

You could verify using the netlify preview, here -- or just wait for the site to refresh (it does seem to be taking a long time).

[dblevins]

I've gone through the netlify specification website page and verified all the links are valid. I'll leave it unchecked till we actually see that page live, however.

[dblevins]

Page is updated now and looks good.