Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add notes about default track #4

Merged
merged 2 commits into from
Mar 11, 2021
Merged

Add notes about default track #4

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
d6313b7
add notes about default track
rvagg Mar 8, 2021
bf11875
Update README.md
rvagg Mar 9, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 10 additions & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down Expand Up @@ -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.
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
rvagg marked this conversation as resolved.
Show resolved Hide resolved

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.