diff options
| author | herrb <herrb@web> | 2020-12-01 17:21:22 +0000 |
|---|---|---|
| committer | IkiWiki <ikiwiki.info> | 2020-12-01 17:21:22 +0000 |
| commit | da9c8bc583f47d4af6db85c7ae2ec420507e117a (patch) | |
| tree | 834eb8fb163c7cc391834249e08a3788bdfd5894 /Development | |
| parent | 6f7424e31e93e6e4777d90b74cc12c1905e3db4a (diff) | |
cgit -> gitlab
Diffstat (limited to 'Development')
| -rw-r--r-- | Development/Development/Security/Checklist.mdwn | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Development/Development/Security/Checklist.mdwn b/Development/Development/Security/Checklist.mdwn index 1a090142..61daed1c 100644 --- a/Development/Development/Security/Checklist.mdwn +++ b/Development/Development/Security/Checklist.mdwn @@ -22,7 +22,7 @@ This page describes the list of things to do when going from a reported bug to a > INCLUDE ADVISORY TEXT HERE 1. Start preparing the patches, notify the master and stable branch maintainers 1. On the day of the embargo, notify the master branch maintainer to push the patches -1. Add the cgit commit links to the advisory text +1. Add the gitlab commit links to the advisory text 1. Send an email to **xorg-announce** with CC to **xorg** and **xorg-devel** with the subject line *"X.Org Security Advisory: CVE-XXXX-YYYY: **blah**"*" with **blah** being the title and the advisory text as content. CC the reporter. 1. Forward the announcement to **[[oss-security@lists.openwall.com|http://oss-security.openwall.org/wiki/mailing-lists]]** (the public counterpart to the private distros list). 1. Edit the [[Security|/Development/Security]] page to include the advisory. |