diff options
| author | Rod Vagg <rod@vagg.org> | 2021-03-11 14:27:34 +1100 |
|---|---|---|
| committer | Rod Vagg <rod@vagg.org> | 2021-03-11 14:28:31 +1100 |
| commit | 1da9032d761fa37514cad23b23940a87048d2312 (patch) | |
| tree | cc73f010ecf6d189c80432a718affbdcc1996646 | |
| parent | 8a6d7a09f2e41e49974450c62de00ceb732e4f8a (diff) | |
| download | node-new-1da9032d761fa37514cad23b23940a87048d2312.tar.gz | |
doc: request default snap track be updated for LTS
Ref: https://github.com/nodejs/snap/pull/4
| -rw-r--r-- | doc/guides/releases.md | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/doc/guides/releases.md b/doc/guides/releases.md index c2eaadbdbe..f6318c181b 100644 --- a/doc/guides/releases.md +++ b/doc/guides/releases.md @@ -881,9 +881,20 @@ test, or doc-related are to be listed as notable changes. Some SEMVER-MINOR commits may be listed as notable changes on a case-by-case basis. Use your judgment there. +### Snap + +The Node.js [Snap] package has a "default" for installs where the user hasn't +specified a release line ("track" in Snap terminology). This should be updated +to point to the most recently activated LTS. A member of the Node.js Build +Infrastructure team is able to perform the switch of the default. An issue +should be opened on the [Node.js Snap management repository] requesting this +take place once a new LTS line has been released. + [Build issue tracker]: https://github.com/nodejs/build/issues/new [CI lockdown procedure]: https://github.com/nodejs/build/blob/HEAD/doc/jenkins-guide.md#restricting-access-for-security-releases [Partner Communities]: https://github.com/nodejs/community-committee/blob/HEAD/governance/PARTNER_COMMUNITIES.md [nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post.js [nodejs.org repository]: https://github.com/nodejs/nodejs.org [webchat.freenode.net]: https://webchat.freenode.net/ +[Snap]: https://snapcraft.io/node +[Node.js Snap management repository]: https://github.com/nodejs/snap |