-
Notifications
You must be signed in to change notification settings - Fork 488
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
Blog post: 4.16.0 #6223
Comments
Hey @ksatter I assigned you this issue and moved it to the current release in the g-community board. Please let me know if I can help contribute to this blog post and CHANGELOG. @mike-j-thomas when you get the chance can you please help us with images for the main blog post tile and the features under the "Primary" improvements section Thanks :) |
Hey @zhumo if you get the chance today, can you please write the "Fleet Desktop out of beta" section for the release post? I think three sentences that describes the improvements made for the stable release makes sense. Please include these sentences in a comment in this issue and mention @ksatter so that Kathy can add this section to the release post :) |
@ksatter, I committed images to #6256. I do not have an image for the following:
and
I do not know what image would be relevant to these, I think you can publish the post without these. |
Fleet 4.16.0 is scheduled for release on 2022-06-16
Primary improvements
Fleet Premium: Custom URL for the "Transparency" link included in Fleet Desktop: #5947
Fleet Premium: Vulnerable software scores including EPSS probability, CVSS base score, and know exploits
Fleet Premium and Fleet Free: Fleet Desktop out of beta: #5684
Fleet Premium and Fleet Free: Ticket workflow for policy automations: #5441
Fleet Premium and Fleet Free: Improvements to the accuracy of vulnerability detections: #5313
Additional improvements
One sentence (bullet) for the issues included in the "Quality assurance," and "Ready for release" columns: https://github.com/orgs/fleetdm/projects/40
The text was updated successfully, but these errors were encountered: