Skip to content
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

chore: Add clarity to SECURITY.md #3154

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

chris-griffin
Copy link

The security policy currently contains a contradiction where it says that the latest release is the only version supported, but also notes that v21.2.0 is not supported. However, according to the repo, v21.2.0 is the latest release.

image

This updates the policy to make it clear that v21.2.0 is currently eligible for security reports as the latest version and also explicitly mentions master as well.

@pajod
Copy link
Contributor

pajod commented Feb 19, 2024

Expression of policy: Consider "At this time.." => "Please target reports against ✅ or current master. Please understand that ❌ will not receive further security attention." and "latest release" => "22.0.0"

Expressed policy: Any specific reason to believe it is worth to invest security attention into what is known to be broken in multiple, somewhat dangerous, places? I would hope that additional fixes are more easily applied on top of what has been merged since, to be used in a future latest release 22.2.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants