-
Notifications
You must be signed in to change notification settings - Fork 721
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
Ensure jdk8 freetype is up to date #16695
Labels
Milestone
Comments
Freetype for jdk11, 17 is still at v2.12, the same version backported to jdk8. Keep this in the 0.38 milestone plan until we get the final levels. |
pshipton
modified the milestones:
Release 0.38 (Java 8, 11, 17) Apr refresh,
Release 0.40 (Java 8, 11, 17, 20) July refresh
Apr 19, 2023
pshipton
modified the milestones:
Release 0.40 (Java 8, 11, 17, 20) July refresh,
Release 0.41 (Java 8, 11, 17) Oct refresh
Jul 20, 2023
pshipton
modified the milestones:
Release 0.41 (Java 8, 11, 17) Oct refresh,
Release 0.43 (Java 8, 11, 17, 21) Jan refresh
Sep 6, 2023
The latest in jdk8 is 2.13.0 |
pshipton
modified the milestones:
Release 0.43 (Java 8, 11, 17, 21) Jan refresh,
Release 0.44 (Java 8, 11, 17, 21) Apr refresh
Jan 17, 2024
@keithc-ca there was an update to 2.13.2 |
Did you not mean to leave this open? The description says it "should not be closed but moved forward". |
Right, I forgot. |
pshipton
modified the milestones:
Release 0.44 (Java 8, 11, 17, 21) Apr refresh,
Release 0.45 (Java 8, 11, 17, 21, 22) July refresh
Feb 27, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This needs to be checked for every release. This issues should not be closed but moved forward.
When freetype in jdk11 is updated, this should be backported to jdk8 as was done in ibmruntimes/openj9-openjdk-jdk8#631
The text was updated successfully, but these errors were encountered: