diff options
| author | Salvatore Bonaccorso <carnil@debian.org> | 2021-02-27 11:24:35 +0100 |
|---|---|---|
| committer | Salvatore Bonaccorso <carnil@debian.org> | 2021-02-27 11:24:35 +0100 |
| commit | d80c6a2ea335aadd312098e30b3f1ca0c226b836 (patch) | |
| tree | 5562336392c8f21ebcb1ab891e70c4dab7a99da0 /doc | |
| parent | 393c57f1cb6523650101ee0c26f39e92d94f6683 (diff) | |
s-t.d.o/triage: Hilight postponed and ignored in code style
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 ca9877fd5f..64e5f77663 100644 --- a/doc/security-team.d.o/triage +++ b/doc/security-team.d.o/triage @@ -21,13 +21,13 @@ If you CC team@security.debian.org for the release.debian.org bug, the fixed ver - 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 committed 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. - Some packages should rather not be fixed at all, e.g. because the possible benefit does not outweigh the risk/costs of an update, or because an update is not possible (e.g. as it would introduce behavioural changes not appropriate for a stable release). In the -Security Tracker these are tracked with the <ignored> state. You can either send a mail to team@security.debian.org and we'll update +Security Tracker these are tracked with the `<ignored>` state. 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. Any of the three actions above will make the CVE ID disappear from the "low severity" entry in the Security Tracker. |