GeezerVison is showing github.com — doc: request default snap track be updated for LTS · nodejs/node@bcc5e2a
File tree
Expand file treeCollapse file tree
Open diff view settings
Expand file treeCollapse file tree
Open diff view settings
Collapse file
Copy file name to clipboardExpand all lines: doc/guides/releases.md +11Lines changed: 11 additions & 0 deletions - Display the source diff
- Display the rich diff
| Original file line number | Diff line number | Diff line change |
|---|
@@ -896,9 +896,20 @@ test, or doc-related are to be listed as notable changes. Some SEMVER-MINOR |
896 | 896 | commits may be listed as notable changes on a case-by-case basis. Use your |
897 | 897 | judgment there. |
898 | 898 |
|
| 899 | +### Snap |
| 900 | + |
| 901 | +The Node.js [Snap][] package has a "default" for installs where the user hasn't |
| 902 | +specified a release line ("track" in Snap terminology). This should be updated |
| 903 | +to point to the most recently activated LTS. A member of the Node.js Build |
| 904 | +Infrastructure team is able to perform the switch of the default. An issue |
| 905 | +should be opened on the [Node.js Snap management repository][] requesting this |
| 906 | +take place once a new LTS line has been released. |
| 907 | + |
899 | 908 | [Build issue tracker]: https://github.com/nodejs/build/issues/new |
900 | 909 | [CI lockdown procedure]: https://github.com/nodejs/build/blob/HEAD/doc/jenkins-guide.md#restricting-access-for-security-releases |
| 910 | +[Node.js Snap management repository]: https://github.com/nodejs/snap |
901 | 911 | [Partner Communities]: https://github.com/nodejs/community-committee/blob/HEAD/governance/PARTNER_COMMUNITIES.md |
| 912 | +[Snap]: https://snapcraft.io/node |
902 | 913 | [nodejs.org release-post.js script]: https://github.com/nodejs/nodejs.org/blob/HEAD/scripts/release-post.js |
903 | 914 | [nodejs.org repository]: https://github.com/nodejs/nodejs.org |
904 | 915 | [webchat.freenode.net]: https://webchat.freenode.net/ |