From 014b0b9ef89f057470db1d16f667e56a47a9796a Mon Sep 17 00:00:00 2001 From: Richard Lau Date: Fri, 5 Jun 2020 11:18:34 +0100 Subject: [PATCH 1/2] Fix broken link to release team --- Security-Team.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Security-Team.md b/Security-Team.md index edabdc7b..f826e418 100644 --- a/Security-Team.md +++ b/Security-Team.md @@ -16,7 +16,7 @@ The policy for inclusion is as follows: 1. All members of @nodejs/TSC have access to private security reports and private patches. -2. Members of the [release team](https://github.com/nodejs/node#release-team) +2. Members of the [release team](https://github.com/nodejs/node#release-keys) have access to private security patches in order to produce releases. 3. On a case-by-case basis, individuals outside the Technical Steering Committee are invited by the TSC to have access to private security reports From 7e79bc204a0e59b21a6718056c69f9d366bfaf61 Mon Sep 17 00:00:00 2001 From: Richard Lau Date: Fri, 5 Jun 2020 14:45:58 +0100 Subject: [PATCH 2/2] fixup! Fix broken link to release team --- Security-Team.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Security-Team.md b/Security-Team.md index f826e418..75b59296 100644 --- a/Security-Team.md +++ b/Security-Team.md @@ -16,7 +16,7 @@ The policy for inclusion is as follows: 1. All members of @nodejs/TSC have access to private security reports and private patches. -2. Members of the [release team](https://github.com/nodejs/node#release-keys) +2. Members of the @nodejs/releasers team have access to private security patches in order to produce releases. 3. On a case-by-case basis, individuals outside the Technical Steering Committee are invited by the TSC to have access to private security reports