-
-
Notifications
You must be signed in to change notification settings - Fork 127
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
January 2025 release blog #3360
Conversation
✅ Deploy Preview for eclipsefdn-adoptium ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #3360 +/- ##
=======================================
Coverage 99.45% 99.45%
=======================================
Files 90 90
Lines 4770 4770
Branches 637 637
=======================================
Hits 4744 4744
Misses 26 26 ☔ View full report in Codecov by Sentry. |
Note to whoever merges this. Please raise the same blog PR to https://github.com/adoptium/adoptium.net-redesign when merged |
content/blog/eclipse-temurin-8u442-11026-17014-2106-2302-available/index.md
Outdated
Show resolved
Hide resolved
content/blog/eclipse-temurin-8u442-11026-17014-2106-2302-available/index.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Adding some comments and also needs the section on the new Docker containers that were added
|
||
### Linux installation packages improvements | ||
|
||
The process for generating our Linux packages (available using these instructions) has been significantly improved in this release. During previous release cycles, the .deb, .rpm & .apk installer packages have not been produced until all architectures for each of the in-support Temurin versions have been completely tested and shipped as .tar.gz files. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
'these instructions' should be hyperlinked to some instructions?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure we've got any instructions written yet, but my 2¢ worth is that it's probably not critical for end users to have that. I've encouraged Scott to do a separate blog on the topic to cover that.
content/blog/eclipse-temurin-8u442-11026-17014-2106-2302-available/index.md
Outdated
Show resolved
Hide resolved
content/blog/eclipse-temurin-8u442-11026-17014-2106-2302-available/index.md
Outdated
Show resolved
Hide resolved
Interesting, the build can't cope with multiple authors |
This line needs either to have a hyperlink to the instructions, or remove the "available using these instructions" bit |
SLSA level 3 is actually called SLSA build level 3 and I would have hyperlinked the https://slsa.dev/spec/v1.0/levels#build-l3 for that phrase rather than add the last sentence, but if you leave it as "More information on SLSA build levels can be found here https://slsa.dev/spec/v1.0/levels#build-l3" add a period to the end of that sentence. |
One other section that the PMC suggested be added into New and Notable was the additional containers (alpine-linux and windows ) can someone please dig that up? |
content/blog/eclipse-temurin-8u442-11026-17014-2106-2302-available/index.md
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Think this still needs a section added for the container changes, but in the interest in getting something out, approving with the idea that the section can be added later.
npm test
passes#3351
@andrew-m-leonard is there anything you would like to add about Redist DLLs for versions? I havent added much on that
@sxa anything else to add regarding SLSA level 3 compliance?