From d6313b7514a2a819c7d636eed42a2b32f4dfd913 Mon Sep 17 00:00:00 2001 From: Rod Vagg Date: Tue, 9 Mar 2021 08:50:47 +1100 Subject: [PATCH 1/2] add notes about default track --- README.md | 11 ++++++++++- 1 file changed, 10 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index a02c31004..4114dd963 100644 --- a/README.md +++ b/README.md @@ -17,6 +17,7 @@ The Snap managed from this repository is available as `node` from the Snap store * [Building Snaps](#building-snaps) * [Adding new release lines](#adding-new-release-lines) * [Removing old release lines](#removing-old-release-lines) + * [Default release line](#default-release-line) ## Installation @@ -111,4 +112,12 @@ Note that at the time of writing, Snap store authorization for Launchpad has an #### Removing old release lines -When release lines stop seeing new releases, they can be removed from [.github/workflows/cron.yml](./.github/workflows/cron.yml). This stops the entire pipeline from running (although changes to the relevant branch will not even occur without new releases on nodejs.org). The Snap configuration in Launchpad can also be removed but this is not strictly necessary. \ No newline at end of file +When release lines stop seeing new releases, they can be removed from [.github/workflows/cron.yml](./.github/workflows/cron.yml). This stops the entire pipeline from running (although changes to the relevant branch will not even occur without new releases on nodejs.org). The Snap configuration in Launchpad can also be removed but this is not strictly necessary. + +### Default release line + +Snaps can have a "default" track. This default determines which track is installed if the user doesn't set one (e.g. with s`sudo snap install node`). It is up to the Snap author to set this default and update it as appropriate. Users don't follow the default track, it only determines the starting track at time of install. Changing default in the Snap store doesn't impact existing users, only new installs + +The Node.js Snap should have its "default" set to the most recent LTS. This can be done in the Releases page by a Node.js Snap administrator: https://snapcraft.io/node/releases and should be done as soon as a release line enters **Active LTS** as per the [Release Schedule](https://github.com/nodejs/release#release-schedule). + +This is a manual procedure and may require reminders posted to this repository from the community. From bf118755ea65d32955360dd6c0c5cfd6df791689 Mon Sep 17 00:00:00 2001 From: Rod Vagg Date: Tue, 9 Mar 2021 22:25:00 +1100 Subject: [PATCH 2/2] Update README.md Co-authored-by: Richard Lau --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 4114dd963..8f8057d59 100644 --- a/README.md +++ b/README.md @@ -116,7 +116,7 @@ When release lines stop seeing new releases, they can be removed from [.github/w ### Default release line -Snaps can have a "default" track. This default determines which track is installed if the user doesn't set one (e.g. with s`sudo snap install node`). It is up to the Snap author to set this default and update it as appropriate. Users don't follow the default track, it only determines the starting track at time of install. Changing default in the Snap store doesn't impact existing users, only new installs +Snaps can have a "default" track. This default determines which track is installed if the user doesn't set one (e.g. with `sudo snap install node`). It is up to the Snap author to set this default and update it as appropriate. Users don't follow the default track, it only determines the starting track at time of install. Changing default in the Snap store doesn't impact existing users, only new installs The Node.js Snap should have its "default" set to the most recent LTS. This can be done in the Releases page by a Node.js Snap administrator: https://snapcraft.io/node/releases and should be done as soon as a release line enters **Active LTS** as per the [Release Schedule](https://github.com/nodejs/release#release-schedule).