diff --git a/docs/contributing/release-process.md b/docs/contributing/release-process.md index 2063533..41598eb 100644 --- a/docs/contributing/release-process.md +++ b/docs/contributing/release-process.md @@ -2,25 +2,23 @@ This document contains the technical aspects of the Express release process. The intended audience is those who have been authorized by the Express Technical -Committee (TC) to create, promote and sign official release builds for Express, -as npm packages hosted on . +Committee (TC) to create, promote and sign official release builds for any +package governed by Express. ## Who can make releases? -Release authorization is given by the Express TC. Once authorized, an individual -must have the following access permissions: +Release authorization is given by the Express TC or by the captains of the package +to be released. Once authorized, an individual must have the following access permissions: ### 1. Github release access -The individual making the release will need to be a member of the -expressjs/express team with Write permission level so they are able to tag the -release commit and push changes to the expressjs/express repository -(see Steps 4 and 5). +The person making the release must be either the package captain or a member of the TC in +order to have sufficient permissions to do the work. ### 2. npmjs.com release access The individual making the release will need to be made an owner on the -`express` package on npmjs.com so they are able to publish the release +package on npmjs.com so they are able to publish the release (see Step 6). ## How to publish a release