Skip to content

Repository navigation

docs(security): extend code freeze from 7 to 10 days #25

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.

Sign up for GitHub

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

Merged
mattac21 merged 2 commits into from
Oct 7, 2026
Merged

docs(security): extend code freeze from 7 to 10 days #25

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d8769a3
extend code freeze from 7 to 10 days
mattac21 Oct 7, 2026
f68f34a
update critical severity section
mattac21 Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -156,9 +156,9 @@ release.

### Code freeze and public release

The private repositories are frozen for the last week of each month. During the
freeze no further patches are merged into that month's repositories. They go
into the next month's set instead, which is created seven days before the month
The private repositories are frozen for the last 10 days of each month. During
Comment thread
mattac21 marked this conversation as resolved.
the freeze no further patches are merged into that month's repositories. They
go into the next month's set instead, which is created 10 days before the month
begins so that it is ready to receive them.

At the start of the following month, every patch in the frozen repositories is
Expand All @@ -174,7 +174,7 @@ retention does not extend anyone's access.

As an example, a vulnerability reported on August 12 and patched on August 15
reaches the private repositories the same week. Those repositories freeze on
August 25, their patches go public on September 1, and the repositories come
August 22, their patches go public on September 1, and the repositories come
down on September 15.

### Critical vulnerabilities
Expand All @@ -184,7 +184,7 @@ through the security mailing list for that repository that the month's private
repository contains a critical patch. And a critical is not merged into a
month's repository within three days of its freeze; one that would be goes into
the next month's repository instead, which pushes its public release out by a
month. Together with the week-long freeze, that leaves at least ten days between
month. Together with the 10 day long freeze, that leaves at least 13 days between
a critical landing in a private repository and its public release.

### Active exploitation
Expand Down
Loading