Skip to content

Commit e832cf7

Browse files
authored
docs: clarify release authorization and permissions in release process (#387)
* docs: clarify release authorization and permissions in release process Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com> * docs: enhance clarity and detail in release process documentation Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com> * Revert "docs: enhance clarity and detail in release process documentation" This reverts commit 891cdf7. * docs: simplify the changes Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com> * formmat Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com> --------- Signed-off-by: Sebastian Beltran <bjohansebas@gmail.com>
1 parent e52abe3 commit e832cf7

1 file changed

Lines changed: 9 additions & 9 deletions

File tree

docs/contributing/release-process.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -2,25 +2,25 @@
22

33
This document contains the technical aspects of the Express release process. The
44
intended audience is those who have been authorized by the Express Technical
5-
Committee (TC) to create, promote and sign official release builds for Express,
6-
as npm packages hosted on <https://npmjs.com/package/express>.
5+
Committee (TC) to create, promote and sign official release builds for any
6+
package governed by Express.
77

88
## Who can make releases?
99

10-
Release authorization is given by the Express TC. Once authorized, an individual
11-
must have the following access permissions:
10+
According to project governance, only package Captains or members of the Technical
11+
Committee (TC) are permitted to make releases. Captains have the freedom to make releases
12+
for their own package whenever necessary, while TC members may make releases for any package
13+
as needed.
1214

1315
### 1. Github release access
1416

15-
The individual making the release will need to be a member of the
16-
expressjs/express team with Write permission level so they are able to tag the
17-
release commit and push changes to the expressjs/express repository
18-
(see Steps 4 and 5).
17+
The person making the release must be either the package captain or a member of the TC in
18+
order to have sufficient permissions to do the work.
1919

2020
### 2. npmjs.com release access
2121

2222
The individual making the release will need to be made an owner on the
23-
`express` package on npmjs.com so they are able to publish the release
23+
package on npmjs.com so they are able to publish the release
2424
(see Step 6).
2525

2626
## How to publish a release

0 commit comments

Comments
 (0)