diff options
| author | Myles Borins <mylesborins@google.com> | 2018-06-29 18:49:42 -0400 |
|---|---|---|
| committer | Myles Borins <mylesborins@google.com> | 2018-07-13 16:06:30 -0400 |
| commit | 7570ad58e91f0cbcf81daf3cdb7e4928b224249e (patch) | |
| tree | e49a95cab85f11b8e222ed8eb4f0a5dffff9eab0 /doc/guides | |
| parent | 2d950701a14638480d0e375180e6dff4b50a709b (diff) | |
| download | android-node-v8-7570ad58e91f0cbcf81daf3cdb7e4928b224249e.tar.gz android-node-v8-7570ad58e91f0cbcf81daf3cdb7e4928b224249e.tar.bz2 android-node-v8-7570ad58e91f0cbcf81daf3cdb7e4928b224249e.zip | |
doc: add policy for landing new npm releases
This change in policy sets clear terms for when / how npm releases
can be landed into master and how long they are expected to bake in the
ecosystem. This is to cover all release types of npm including semver-major
releases.
What Node.js releases the updates land into are at the discretion of the
release team.
PR-URL: https://github.com/nodejs/node/pull/21594
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Franziska Hinkelmann <franziska.hinkelmann@gmail.com>
Reviewed-By: Tiancheng "Timothy" Gu <timothygu99@gmail.com>
Diffstat (limited to 'doc/guides')
| -rw-r--r-- | doc/guides/maintaining-npm.md | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/guides/maintaining-npm.md b/doc/guides/maintaining-npm.md index 97da87feee..6017e78fde 100644 --- a/doc/guides/maintaining-npm.md +++ b/doc/guides/maintaining-npm.md @@ -1,5 +1,19 @@ # Maintaining npm in Node.js +New pull requests should be opened when a "next" version of npm has +been released. Once the "next" version has been promoted to "latest" +the PR should be updated as necessary. + +Two weeks after the "latest" release has been promoted it can land on master +assuming no major regressions are found. There are no additional constraints +for Semver-Major releases. + +The specific Node.js release streams the new version will be able to land into +are at the discretion of the release and LTS teams. + +This process only covers full updates to new versions of npm. Cherry-picked +changes can be reviewed and landed via the normal consensus seeking process. + ## Step 1: Clone npm ```console |