Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Publish Jakarta Transactions 2.0 #183

Closed
5 tasks done
dblevins opened this issue Nov 5, 2020 · 13 comments
Closed
5 tasks done

Publish Jakarta Transactions 2.0 #183

dblevins opened this issue Nov 5, 2020 · 13 comments
Labels

Comments

@dblevins
Copy link
Contributor

dblevins commented Nov 5, 2020

I hadn't realized we added this finishing step, so many of these items may already be done.

  • 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.
  • 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.
@tomjenkinson
Copy link
Contributor

Thanks @dblevins - do you know what we need to do with "approve the compatibility request" - is it something on #180 ?

@dblevins
Copy link
Contributor Author

dblevins commented Nov 5, 2020

@tomjenkinson slap an "accepted" label on the issue and you're good to go :)

@tomjenkinson
Copy link
Contributor

Great - thanks!

@tomjenkinson
Copy link
Contributor

@smillidge @arjantijms do you know who will be sending the email to tck@eclipse.org, regarding Glassfish and approval for it as compatible implementation for trademark usage and when that can be expected / tracked? Thanks!

(some background in jakartaee/specifications#25)

@tomjenkinson
Copy link
Contributor

It seems that the Glassfish version we certified with (https://download.eclipse.org/ee4j/glassfish/weekly/glassfish-6.0.0-SNAPSHOT-2020-10-04.zip) is no longer available from https://download.eclipse.org/ee4j/glassfish/weekly/

@dblevins - do you think I should update that link to https://ci.eclipse.org/jta/job/TCK_raw-glassfish/12/ as that has an archived version of that version of Glassfish (https://ci.eclipse.org/jta/job/TCK_raw-glassfish/12/console)?

@tomjenkinson
Copy link
Contributor

Checked "merge any final release branch as appropriate for the branch management for the project" having merged #183 (although it wasn't directly a branch before)

@arjantijms
Copy link
Contributor

@tomjenkinson
Copy link
Contributor

Thanks! I will raise a PR on the specifications repo

@tomjenkinson
Copy link
Contributor

Thanks again, I have a PR to update the link: jakartaee/specifications#306

@tomjenkinson
Copy link
Contributor

@arjantijms I think you might have done something like this before for Jakarta Transactions 1.3 (jakartaee/specifications#25); would you be able to help us fulfil "The compatible implementation project/vendor MUST send an email to tck@eclipse.org for approval of the compatible implementation for trademark usage." please? I expect someone needs to send it on behalf of the specifications compatible implementation Glassfish and as I am not listed on https://projects.eclipse.org/projects/ee4j.glassfish/who I doubt it can be me /cc @dblevins @smillidge

@arjantijms
Copy link
Contributor

@tomjenkinson Indeed, I've sent these mails before. I'm on it.

@arjantijms
Copy link
Contributor

@tomjenkinson mail sent. CC'ed you and Steve (GF lead).

@tomjenkinson
Copy link
Contributor

Thanks @arjantijms ! BTW the message you sent (Approval to claim Jakarta Transactions compatibility for GlassFish 6.0.0-M3-2020-10-04) I didn't see Steve cc'd but it might just be how it arrived to me perhaps? Thanks again and I will tick the box in the initial comment and close this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants