From 4c07194185b6f9f5da6c686e9de951404c8e3347 Mon Sep 17 00:00:00 2001 From: Salvatore Bonaccorso Date: Sat, 27 Feb 2021 11:34:14 +0100 Subject: s-t.d.o/triage: Add reference for proposed update mechanism --- doc/security-team.d.o/triage | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/security-team.d.o/triage b/doc/security-team.d.o/triage index 7a1a819cc0..a45407efc4 100644 --- a/doc/security-team.d.o/triage +++ b/doc/security-team.d.o/triage @@ -3,8 +3,7 @@ Security updates affecting a released Debian suite can fall under three types: - The security issue(s) are important enough to warrant an out-of-band update released via [security.debian.org](https://www.debian.org/security/) which gets announced as a DSA. These are getting announced via [debian-security-announce](https://www.debian.org/security/) and also redistributed via other sources (news feeds etc). -- Low severity updates can be included in [point releases](https://wiki.debian.org/DebianReleases/PointReleases), which are getting released every 2-3 months (any user using the -proposed-updates - mechanism can also use them before they get released). This provides a good balance between fixing low impact issues before the next stable +- Low severity updates can be included in [point releases](https://wiki.debian.org/DebianReleases/PointReleases), which are getting released every 2-3 months (any user using the [proposed-updates mechanism](https://www.debian.org/releases/proposed-updates) can also use them before they get released). This provides a good balance between fixing low impact issues before the next stable release, which can simply all be installed in one go when a point release happens. - Some issues are simply not worth fixing in a stable release (for multiple reasons, e.g. because they are mostly a PR hype, or because they -- cgit v1.2.3