diff options
| author | Salvatore Bonaccorso <carnil@debian.org> | 2021-02-27 11:13:44 +0100 |
|---|---|---|
| committer | Salvatore Bonaccorso <carnil@debian.org> | 2021-02-27 11:13:44 +0100 |
| commit | 393c57f1cb6523650101ee0c26f39e92d94f6683 (patch) | |
| tree | 71c75f3eb001d97f82a1f3ef2119c2dc0e1a41ca /doc | |
| parent | 8fe869ddf128e8080a4d9c17dcb256982e8182a5 (diff) | |
s-t.do/tirage: Fis some spelling errors in draft
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/security-team.d.o/triage | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/security-team.d.o/triage b/doc/security-team.d.o/triage index 948026899a..ca9877fd5f 100644 --- a/doc/security-team.d.o/triage +++ b/doc/security-team.d.o/triage @@ -17,11 +17,11 @@ For every CVE listed there, there are three possible options: - Prepare an update for the next point release following: https://www.debian.org/doc/manuals/developers-reference/pkgs.en.html#special-case-uploads-to-the-stable-and-oldstable-distributions -If you CC team@security.debian.org for the release.debian.org bug, the fixed version will get recorded in the Debian Securiy Tracker. +If you CC team@security.debian.org for the release.debian.org bug, the fixed version will get recorded in the Debian Security Tracker. - Some packages have a steady flow of security issues and there's also the option to postpone an update to a later time, in other words to get piggybacked onto a future DSA dedicated to a more severe security issue, or held back until a few more low severity issues are known. In the -Security Tracker these are tracked with the <postponed> state, often this means that a fix has been commited to e.g. a buster branch +Security Tracker these are tracked with the <postponed> state, often this means that a fix has been committed to e.g. a buster branch in salsa, but no upload has been made yet. You can either send a mail to team@security.debian.org and we'll update the state, or you can also make the change yourself if you're familiar with the Security Tracker. |