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.

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

schedule: give v12.x LTS its codename #488

Merged
merged 1 commit into from
Oct 21, 2019
Merged

schedule: give v12.x LTS its codename #488

merged 1 commit into from
Oct 21, 2019

Conversation

targos
Copy link
Member

@targos targos commented Oct 15, 2019

Draft because I think it shouldn't land before 12.13.0 is released.

@targos
Copy link
Member Author

targos commented Oct 15, 2019

is https://nodejs.org/download/release/latest-erbium/ going to be automatically created or something needs to be manually done?

@@ -156,6 +156,7 @@ only landed in the `v4.x` branch when a new `v4.x` release is being prepared.**
[Boron]: https://nodejs.org/download/release/latest-boron/
[Carbon]: https://nodejs.org/download/release/latest-carbon/
[Dubnium]: https://nodejs.org/download/release/latest-dubnium/
[Erbium]: https://nodejs.org/download/release/latest-erbium/
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We'll need to remember to add erbium to https://github.com/nodejs/nodejs-latest-linker/blob/46a6c7069a2c30028d149985327a34a71e69878e/latest-linker.js#L10-L15 for this link to get created. I'm unsure of the sequencing (whether it should happen before or after the release).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, I opened the PR: nodejs/nodejs-latest-linker#3

@targos targos marked this pull request as ready for review October 21, 2019 09:20
@targos targos merged commit a5b7393 into master Oct 21, 2019
@targos targos deleted the erbium branch October 21, 2019 09:20
@richardlau richardlau mentioned this pull request Nov 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants