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

add node 12 to the first list of versions #27414

Closed
wants to merge 1 commit into from
Closed

add node 12 to the first list of versions #27414

wants to merge 1 commit into from

Conversation

rivajunior
Copy link
Contributor

Checklist

@nodejs-github-bot nodejs-github-bot added the meta Issues and PRs related to the general management of the project. label Apr 25, 2019
@@ -2,7 +2,8 @@

Select a Node.js version below to view the changelog history:

* [Node.js 11](doc/changelogs/CHANGELOG_V11.md) - **Current**
* [Node.js 12](doc/changelogs/CHANGELOG_V12.md) - **Current**
* [Node.js 11](doc/changelogs/CHANGELOG_V11.md) - Current
Copy link
Contributor

Choose a reason for hiding this comment

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

11 should be End-of-Life I think.

Copy link
Member

Choose a reason for hiding this comment

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

Not yet

Copy link
Member

Choose a reason for hiding this comment

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

… but I think Maintenance would be accurate?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, I think it should. See the graphic on https://nodejs.org/en/about/releases/ but in the table, version 11 is with "current" label.

Copy link
Contributor

Choose a reason for hiding this comment

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

Ok, then keep it. It's a bit weird we have two "Current" versions, but I guess that's intended.

@ZYSzys
Copy link
Member

ZYSzys commented Apr 26, 2019

@silverwind
Copy link
Contributor

Merged in e029b92, sorry @ZYSzys.

@silverwind silverwind closed this Apr 26, 2019
silverwind pushed a commit that referenced this pull request Apr 26, 2019
PR-URL: #27414
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
@lpinca
Copy link
Member

lpinca commented Apr 26, 2019

@silverwind the commit landed without a proper subsystem in title.

targos pushed a commit that referenced this pull request Apr 27, 2019
PR-URL: #27414
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Michaël Zasso <targos@protonmail.com>
Reviewed-By: Roman Reiss <me@silverwind.io>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Yongsheng Zhang <zyszys98@gmail.com>
@targos targos mentioned this pull request Apr 27, 2019
@silverwind
Copy link
Contributor

@lpinca yes that occured to me shortly after merging as well. Been a while since I did merges here, will be more careful next time :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta Issues and PRs related to the general management of the project.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants