-
-
Notifications
You must be signed in to change notification settings - Fork 126
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 post #3351
Comments
JSF signing for SBOMs was implemented for this release |
Better automation / major overhaul in how we deliver Linux installers was also introduced in this release. Some re-publishing was required, for those wondering why the multiple releases in artifactory. Can refer to the EPIC for details of the work. (Perhaps get @steelhead31 input on this section of the blog post). |
If it will wait a day or two until I'm back I'll write something suitable. The republishes were largely due to bugs in the automation, not signing packages properly in the base release and the 2nd republish was to fix a broken dependency and the third an issue with the default installation path. |
Also worth mention that we are now SLSA level 3 compliant on all Windows platforms (previously we only had it on Linux and macos - but windows/x64 was the remaining primary). |
@Haroon-Khel / @smlambert / @sxa Some text for the blog post, should you need to do this whilst I'm unwell.. feel free to edit and improve the below, but it sums up the changes in the release.
|
For the purposes of the release blog I'd keep it simpler than that, although we could have a separate blog post talking about the installer improvements :-) I'd suggest this (based on what you had above) Linux installation packages improvementsThe process for generating our Linux packages (available using these instructions) has been significantly improved in this release. During previous release cycles, the As of this release cycle new automation has been put in place which allows the Linux packages to be built and published at the same time as the release tarballs are published to GitHub, so they will be available much sooner than before. |
Thanks @sxa , that sounds like a good plan, and I like the idea of doing a blog post. |
@gdams also mentioned some notable news relating to Docker images |
Issue for Jan 2025 release blog post
The text was updated successfully, but these errors were encountered: