Closed luhenry closed 3 months ago
Name | Link |
---|---|
Latest commit | d14028acf68488f0146adab9b71cbff2c8bf4379 |
Latest deploy log | https://app.netlify.com/sites/eclipsefdn-adoptium/deploys/6607be17b172b50008095ea5 |
Deploy Preview | https://deploy-preview-2745--eclipsefdn-adoptium.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 99.24%. Comparing base (
ddfaa73
) to head (d14028a
). Report is 3 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
I have just shipped JDK22 for RISC-V (It should appear on the website an API in the next day or so) so this can now be modified to say we have both if desired. JDk21 as the LTS release should probably be the headline version but I'm happy with however we wish to make this change @luhenry @CarmenDelgadoEclipse
Let me update the title and content
I also wonder if it's worth referencing any of the FOSDEM talks related to OpenJDK on RISC-V e.g.
I'll probably include those when I share this on social media regardless, but it really depends on whether we want to provide content for the more technical audience who might want to know a bit about some of the things that happen behind the scenes to make a port like this on a complex runtime environment happen.
I don't want to add much more to that message. We should likely write other blog posts, as we can also mention the RISC-V Optimization Manual that is a great resource. Just FYI that these are also already broadcasted by RISC-V International, but of course the more we broadcast these information the better.
Description of change
Checklist
npm test
passes