From b1a3931c99ee3b16288ce1966a2f46619a242dd1 Mon Sep 17 00:00:00 2001 From: Myles Borins Date: Fri, 29 Jun 2018 18:49:42 -0400 Subject: [PATCH 1/2] 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. --- doc/guides/maintaining-npm.md | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/doc/guides/maintaining-npm.md b/doc/guides/maintaining-npm.md index 97da87feee64d3..c4420c46122b49 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 is no additional constraints +for Semver-Major releases. + +The Node.js release streams the new version will 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 From 6db6b532e7561a1bf500f96002c1a5c8f1d40e91 Mon Sep 17 00:00:00 2001 From: Myles Borins Date: Wed, 11 Jul 2018 10:27:21 -0400 Subject: [PATCH 2/2] fixup: minor grammar nits --- doc/guides/maintaining-npm.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/guides/maintaining-npm.md b/doc/guides/maintaining-npm.md index c4420c46122b49..d08c35ec272456 100644 --- a/doc/guides/maintaining-npm.md +++ b/doc/guides/maintaining-npm.md @@ -5,11 +5,11 @@ 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 is no additional constraints +assuming no major regressions are found. There are no additional constraints for Semver-Major releases. -The Node.js release streams the new version will land into are at the -discretion of the release and LTS teams. +The specific Node.js release stream 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.