Skip to content

Add Supported Versions table to SECURITY.md#2312

Open
singhvishalkr wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
singhvishalkr:docs/add-supported-versions-to-security
Open

Add Supported Versions table to SECURITY.md#2312
singhvishalkr wants to merge 1 commit into
AcademySoftwareFoundation:mainfrom
singhvishalkr:docs/add-supported-versions-to-security

Conversation

@singhvishalkr
Copy link
Copy Markdown

This adds a Supported Versions table to SECURITY.md, describing which release branches receive security patches.

I modeled the format on the similar table in OpenImageIO's security policy, as suggested in #2032. The table covers:

  • main branch (all fixes, unstable API/ABI)
  • 2.5.x (all security fixes with ABI compatibility)
  • 2.4.x (critical security fixes only)
  • Older branches (no longer patched)

I based the support status on the recent release activity and the CVE fix history in the document. The TSC can adjust the wording if the actual policy differs from what I've documented.

Fixes #2032

Signed-off-by: Vishal Kumar Singh vishal.kr.singh2021@gmail.com

Add a table describing which release branches receive security patches, following the format used by OpenImageIO.

Fixes AcademySoftwareFoundation#2032

Signed-off-by: Vishal Kumar Singh <vishal.kr.singh2021@gmail.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
@linux-foundation-easycla
Copy link
Copy Markdown

linux-foundation-easycla Bot commented May 16, 2026

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: singhvishalkr / name: Vishal Kumar Singh (563a24c)

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.

Add a Supported Versions table to SECURITY.md

1 participant