Skip to content

Repository navigation

docs: update wording for code freeze #24

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
aljo242 merged 2 commits into from
Oct 2, 2026
Merged

docs: update wording for code freeze #24

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
176b0a5
docs: let the repositories freeze, not the vulnerability
aljo242 Oct 2, 2026
a316040
docs: it is the patches that go public, not the repositories
aljo242 Oct 2, 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
5 changes: 3 additions & 2 deletions SECURITY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -173,8 +173,9 @@ month's repositories is granted by fresh invitation on its own schedule, so the
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, is frozen on August 25, is
public on September 1, and the August repositories come down on September 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
down on September 15.

### Critical vulnerabilities

Expand Down
Loading